ci(release): push CHANGELOG to develop via RELEASE_TOKEN PAT#12
Merged
Conversation
The protect-develop ruleset blocks direct pushes to develop, and the GitHub Actions bot can't be added as a bypass actor on a user-owned repo. Pushing with an admin-owned fine-grained PAT (Contents: read/write) attributes the push to the admin, who is already a bypass actor in the ruleset. Requires a RELEASE_TOKEN repo secret.
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.
The
protect-developruleset blocks direct pushes todevelop, and the GitHub Actions bot cannot be added as a bypass actor on a user-owned (non-org) repo — it's absent from both the API and the UI bypass list.Fix: the changelog job now checks out with a
RELEASE_TOKENPAT. A push authenticated by an admin-owned PAT is attributed to that admin, who is already a bypass actor (RepositoryRole/5, modealways) in the ruleset — so the CHANGELOG push todevelopsucceeds.Required before the next release
Create the secret:
NoiXdev/s3ManagerRELEASE_TOKEN(Settings → Secrets and variables → Actions).No workflow-file changes are pushed by the release job, so
Contentsis the only permission needed.