ci(changelog): open PR instead of pushing to protected main#41
Merged
Conversation
main is now branch-protected (required checks: ci (22), ci (24), analyze, ai-review). github-actions[bot] can't bypass, so the previous direct push would be rejected on the next release. New flow: - Same prepend logic as before - Push to a per-release branch (chore/changelog-<tag>) - Open a PR - Enable auto-merge — squash + delete-branch - CI runs and merges automatically when green Same end state, just routed through the same gate every other change uses.
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.
Summary
Follow-up to applying branch protection (P0 #4 from the audit).
update-changelog.ymlpreviously didgit pushto main directly. With branch protection now requiring 4 status checks before merge, that push would be rejected on the next release. github-actions[bot] is not an admin, so it can't bypass.New flow
chore/changelog-<tag>.gh pr createopens a PR.gh pr merge --squash --auto --delete-branchenables auto-merge.Same end state, routed through the same gate every other change uses.
Test plan