Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport release-1.23] Use a custom GitHub token in the backport action #1961

Merged
merged 1 commit into from
Jul 29, 2022

Conversation

jnummelin
Copy link
Member

Automated backport to release-1.23, triggered by a label in #1960.
See .

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)
@jnummelin jnummelin requested a review from a team as a code owner July 29, 2022 10:26
@jnummelin jnummelin requested review from ncopa and twz123 and removed request for a team July 29, 2022 10:26
@twz123 twz123 changed the title [Backport release-1.23] [Backport release-1.24] Use a custom GitHub token in the backport action [Backport release-1.23] Use a custom GitHub token in the backport action Jul 29, 2022
@twz123 twz123 added bug Something isn't working area/ci backport/release-1.22 PR that needs to be backported/cherrypicked to release-1.22 branch labels Jul 29, 2022
@twz123 twz123 merged commit 1c85782 into release-1.23 Jul 29, 2022
@twz123 twz123 deleted the backport-1960-to-release-1.23 branch July 29, 2022 13:04
@jnummelin
Copy link
Member Author

Successfully created backport PR #1967 for release-1.22.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci backport/release-1.22 PR that needs to be backported/cherrypicked to release-1.22 branch bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants