Replace the GITHUB_TOKEN with a PAT #1072
Merged
Conversation
This file contains 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
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.
This PR will replace
secret.GITHUB_TOKENwithsecret.CB_GITHUB_ROBOT_PAT.(Summary)
GITHUB_TOKENis scoped to the current repository (i.e., forked repo).GITHUB_TOKENdoes NOT have permission to add comments on PRs opened in the upstream repo from the forked repo.CB_GITHUB_ROBOT_PATcan be scoped as desired (reposcope is assigned)CB_GITHUB_ROBOT_PAT.Ref: https://github.com/actions/github-script?tab=readme-ov-file#using-a-separate-github-token
In my opinion, this PR should be merged as is. And then, we can check for permission issues in the next PR.
(Until then, I'd like to keep #1070 open.)