CI: drop the now-unneeded PYDE_REPO_TOKEN from pyde-crypto checkout - #53
Merged
Conversation
pyde-crypto is public now, so the sibling checkout needs no token (the default GITHUB_TOKEN reads public repos). Removes the token from all 5 jobs and the stale continue-on-error workaround, so external fork PRs get green CI once this repo is public.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pyde-crypto is public, so the sibling checkout no longer needs a PAT (the default GITHUB_TOKEN reads public repos). Removed
token: ${{ secrets.PYDE_REPO_TOKEN }}and the stalecontinue-on-errorworkaround from all 5 jobs (clippy, msrv, test, doc, examples), and refreshed the comment. This makes CI pass on external fork PRs once the repo goes public.