Use GITHUB_TOKEN instead of dedicated PUSH_TOKEN in auto-merge workflow #8541
+6
−3
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
Using the temporary
GITHUB_TOKENtoken is better for security, as it get revoked automatically as soon as the workflow ends and is scoped to just this repository, so if it were to somehow get leaked the damage that could be done is much lower and it would only be useable for as long as the workflow is running. This lets us remove the dedicatedPUSH_TOKENtoken.Testing
Successful run here ("github-action[bot] enabled auto-merge (squash)"): absidue#5