Use GH_TOKEN environment variable in auto merge workflow #7656
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.
Pull Request Type
Description
In the auto-merge workflow we currently write the
PUSH_TOKEN
to a file, pipe it into the gh auth login command and then delete that file, these days howevergh
also supports reading the token from theGH_TOKEN
environment variable, which is also the documented way to use gh in GitHub Actions (see link below). This pull request switches to using that environment variable and also disables all permissions for the standardGITHUB_TOKEN
token as we don't use it in this workflow.https://docs.github.com/en/actions/how-tos/writing-workflows/choosing-what-your-workflow-does/using-github-cli-in-workflows
Testing