Use PAT token for release workflow to bypass branch protection#153
Merged
Use PAT token for release workflow to bypass branch protection#153
Conversation
Replace GITHUB_TOKEN with RELEASE_TOKEN secret to allow pushing directly to main branch during automated releases.
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
2 participants
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
Updated the create-release workflow to use a Personal Access Token (PAT) instead of the default GITHUB_TOKEN when checking out the repository. This allows the release process to push commits to protected branches.
Changes
secrets.GITHUB_TOKENwithsecrets.RELEASE_TOKENin the checkout actionDetails
The default GITHUB_TOKEN has limited permissions and cannot push to branches with protection rules enabled. By using a dedicated PAT stored in
RELEASE_TOKEN, the workflow can successfully create and push release commits even when the target branch has protection rules configured (e.g., requiring status checks or code reviews).Note: The
RELEASE_TOKENsecret must be configured in the repository settings with appropriate permissions before this workflow will function.