fix(ci): use BOT_PR_TOKEN for collect-lime-results PR flow - #86
Merged
Conversation
The org disables "write" workflow permissions, so the default GITHUB_TOKEN cannot open PRs or call gh pr merge --auto. Use the BOT_PR_TOKEN PAT (Contents + Pull Requests: write on this repo) for the PR-creating and merging steps. Checkout keeps GITHUB_TOKEN because it only needs to read the working tree.
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
Swap the default `GITHUB_TOKEN` for the new `BOT_PR_TOKEN` PAT on the steps that create and auto-merge the bot PR. Checkout keeps `GITHUB_TOKEN`.
Why
The org has "Allow GitHub Actions to create and approve pull requests" disabled, so `GITHUB_TOKEN` cannot open PRs or call `gh pr merge --auto`. We can't toggle that at the repo level. `BOT_PR_TOKEN` is a user PAT with Contents + Pull Requests: write on this repo only.
Test plan