Use PAT token for release workflow to bypass branch protection#86
Merged
Use PAT token for release workflow to bypass branch protection#86
Conversation
…rules The default GITHUB_TOKEN cannot push to main when repository rulesets require the "Apify pull request toolkit" workflow (which only runs on PRs). Using a PAT at checkout time allows git push to bypass this restriction. https://claude.ai/code/session_01Jhq1SCwkA8r1PBoTMSMmR9
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
3 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 release workflow to use a Personal Access Token (PAT) instead of the default
GITHUB_TOKENwhen checking out the repository. This allows the release job to push version-bump commits and tags directly to main, bypassing branch protection rulesets that block the default token.Key Changes
.github/workflows/release.ymlto addtoken: ${{ secrets.RELEASE_PAT }}to the checkout actionImplementation Details
The change leverages GitHub Actions' support for custom tokens in the checkout action. By using a PAT stored in
secrets.RELEASE_PAT, the release workflow can perform protected operations (pushing commits and tags to main) that would otherwise be blocked by branch protection rulesets configured to restrict the defaultGITHUB_TOKEN.https://claude.ai/code/session_01Jhq1SCwkA8r1PBoTMSMmR9