Repository navigation
Support custom token for triggering CI on version PRs - #11
Merged
Merged
Conversation
Commits pushed with GITHUB_TOKEN don't trigger workflow runs due to GitHub's anti-recursion guard. After the normal git push, recreate the tip commit via the GitHub REST API and force-update the branch ref so that pull_request workflows fire automatically — no PATs, GitHub Apps, or changes to user CI configs needed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The changes in this PR will be included in the next version bump.
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
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.


Summary
BUMPY_GH_TOKENenv var — when set, bumpy pushes the version branch using the custom token, bypassing GitHub's anti-recursion guard so PR workflows fire automaticallybumpy ci setupinteractive command that walks users through creating a fine-grained PAT or GitHub App and stores it as a repo secret viagh secret setBUMPY_GH_TOKENis only used for the git push — PR comments and otherghCLI calls continue using the defaultGITHUB_TOKENso they appear as the Actions botactions/checkoutextraheader during push so the custom token is actually used (nopersist-credentials: falseneeded)Test plan
bumpy ci setuplocally, verify PAT flow works end-to-endBUMPY_GH_TOKENsecret, merge a changeset, verify version PR triggers CI checksBUMPY_GH_TOKENset — verify warning is logged🤖 Generated with Claude Code