[Backport release-1.22] Use a custom GitHub token in the backport action #1967
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
Due to a limitation of the GitHub Actions default tokens, Pull Requests opened with them won't trigger any events. Hence, they won't trigger the CI builds. Use a custom token to circumvent that and let backport PRs be built on CI. Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com> (cherry picked from commit 97d26b2) (cherry picked from commit e019731) (cherry picked from commit 504bce0)
twz123
changed the title
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.
Automated backport to
release-1.22, triggered by a label in #1961.See .