Fix the automatic ID allocation workflow.#3612
Merged
Conversation
The automatic ID allocation workflow currently cannot be used in fully automated mode (after a PR has been merged), because it will always use the default GITHUB_TOKEN, which is not allowed to push to the master branch. The action has a dedicated token (which should be allowed to push to the master branch) specifically intended for the purpose of automatic ID allocation, but for the push step to use it, the checkout step needs to be configured _not_ to persist the checkout credentials, which is what we do here.
matentzn
approved these changes
Sep 15, 2025
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
2 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.
The automatic ID allocation workflow currently cannot be used in fully automated mode (after a PR has been merged), because it will always use the default
GITHUB_TOKEN, which is not allowed to push to the master branch.The workflow has a dedicated token (which is allowed to push to the master branch) specifically intended for the purpose of automatic ID allocation, but for the push step to use it, the checkout step needs to be configured not to persist the checkout credentials, which is what we do here.