Skip to content

Backport 4.1: Backport PRs must be created with personal access tokens#16277

Merged
chrisvest merged 1 commit into4.1from
backport-pr-16276-to-4.1
Feb 16, 2026
Merged

Backport 4.1: Backport PRs must be created with personal access tokens#16277
chrisvest merged 1 commit into4.1from
backport-pr-16276-to-4.1

Conversation

@chrisvest
Copy link
Copy Markdown
Member

Backport of #16276 to 4.1
Cherry-picked commit: ca25641


Motivation:
When creating a PR using a workflow GITHUB_TOKEN, then no additional workflows are triggered. This means our CI build is not started on automatic backport PRs:
https://docs.github.com/en/actions/concepts/security/github_token#when-github_token-triggers-workflow-runs

Modification:
Use a personal access token when creating the backport PR, instead of GITHUB_TOKEN.

Result:
Backport PRs should now have CI triggered.

Motivation:
When creating a PR using a workflow GITHUB_TOKEN, then no additional
workflows are triggered. This means our CI build is not started on
automatic backport PRs:

https://docs.github.com/en/actions/concepts/security/github_token#when-github_token-triggers-workflow-runs

Modification:
Use a personal access token when creating the backport PR, instead of
GITHUB_TOKEN.

Result:
Backport PRs should now have CI triggered.

(cherry picked from commit ca25641)
@chrisvest
Copy link
Copy Markdown
Member Author

@normanmaurer Using a personal access token does indeed let the CI builds run, but also makes it look like I posted the PR. So we should ideally get a token from the @netty-project-bot account. I don't have access to that account, but I can show you how to create it.

@normanmaurer
Copy link
Copy Markdown
Member

@normanmaurer Using a personal access token does indeed let the CI builds run, but also makes it look like I posted the PR. So we should ideally get a token from the @netty-project-bot account. I don't have access to that account, but I can show you how to create it.

Let's catch up on Monday and do so ...

@chrisvest chrisvest added this to the 4.1.132.Final milestone Feb 16, 2026
@chrisvest chrisvest merged commit b80ae68 into 4.1 Feb 16, 2026
33 of 34 checks passed
@chrisvest chrisvest deleted the backport-pr-16276-to-4.1 branch February 16, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants