ci: use PAT for release-please so Release PRs trigger CI#4
Closed
ParzivalEugene wants to merge 1 commit into
Closed
ci: use PAT for release-please so Release PRs trigger CI#4ParzivalEugene wants to merge 1 commit into
ParzivalEugene wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing: going with admin-merge for release PRs (zero extra machinery, no long-lived secret) instead of a PAT. |
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.
Release PRs opened by release-please used the default GITHUB_TOKEN, so GitHub suppressed CI on them (recursion guard) and the required
testcheck stayed forever pending (this blocked the 0.1.2 release PR).Switches the action to a PAT (
RELEASE_PLEASE_TOKEN) so its PRs trigger CI normally. Also addsworkflow_dispatchto allow a manual release run.