ci(bump-version): skip push on protected main instead of failing#5
Merged
Conversation
The bump-on-merge workflow only ever targets main (its sole trigger is PRs into main), which is a protected branch — the github-actions bot cannot push directly, so the 'Commit and push bump' step failed on every merge. Gate the push: when the base branch is main, log a notice and exit 0 instead of attempting a rejected push. Pushes to unprotected branches are unchanged. Also move base.ref into a quoted env var (BASE_REF).
✅ Deploy Preview for bazgaars-fmg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
The bump-on-merge workflow only ever targets
main(its sole trigger is PRs into main), a protected branch. Thegithub-actions[bot]can't push directly, so the Commit and push bump step failed on every merge (e.g. run 27233465820).This gates the push: when the base branch is
main, it logs a::notice::and exits 0 instead of attempting a rejected push. Pushes to unprotected branches are unchanged. Also movesbase.refinto a quotedenvvar (BASE_REF) per the safe-interpolation pattern.