ci: allow backport workflow to use a PAT to trigger downstream CI#853
Merged
mcottontensor merged 1 commit intoEpicGamesExt:masterfrom May 1, 2026
Merged
Conversation
…icGamesExt#655) PRs opened with the default GITHUB_TOKEN do not trigger downstream pull_request workflows (an anti-recursion safeguard), which is why backport PRs land without CI running on them. Read the github_token from BACKPORT_PAT first and fall back to GITHUB_TOKEN, so configuring a repo/org secret named BACKPORT_PAT (PAT with repo scope) unlocks CI on backport PRs without any further code change. Behavior is unchanged when the secret is not configured.
|
mcottontensor
added
auto-backport
Collaborator
Author
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
This was referenced May 1, 2026
Collaborator
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
mcottontensor
added a commit
that referenced
this pull request
May 1, 2026
…) (#853) (#855) PRs opened with the default GITHUB_TOKEN do not trigger downstream pull_request workflows (an anti-recursion safeguard), which is why backport PRs land without CI running on them. Read the github_token from BACKPORT_PAT first and fall back to GITHUB_TOKEN, so configuring a repo/org secret named BACKPORT_PAT (PAT with repo scope) unlocks CI on backport PRs without any further code change. Behavior is unchanged when the secret is not configured. (cherry picked from commit 9d9db1d)
mcottontensor
added a commit
that referenced
this pull request
May 1, 2026
…) (#853) (#856) PRs opened with the default GITHUB_TOKEN do not trigger downstream pull_request workflows (an anti-recursion safeguard), which is why backport PRs land without CI running on them. Read the github_token from BACKPORT_PAT first and fall back to GITHUB_TOKEN, so configuring a repo/org secret named BACKPORT_PAT (PAT with repo scope) unlocks CI on backport PRs without any further code change. Behavior is unchanged when the secret is not configured. (cherry picked from commit 9d9db1d)
mcottontensor
added a commit
that referenced
this pull request
May 1, 2026
…) (#853) (#857) PRs opened with the default GITHUB_TOKEN do not trigger downstream pull_request workflows (an anti-recursion safeguard), which is why backport PRs land without CI running on them. Read the github_token from BACKPORT_PAT first and fall back to GITHUB_TOKEN, so configuring a repo/org secret named BACKPORT_PAT (PAT with repo scope) unlocks CI on backport PRs without any further code change. Behavior is unchanged when the secret is not configured. (cherry picked from commit 9d9db1d)
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.
Summary
github_tokenfromsecrets.BACKPORT_PAT || secrets.GITHUB_TOKENin.github/workflows/backport.yml.BACKPORT_PATis not set.BACKPORT_PATis configured (a PAT withreposcope), backport PRs will trigger downstreampull_requestworkflows like the rest of CI.GitHub deliberately doesn't fire
pull_requestevents for PRs opened with the defaultGITHUB_TOKEN(anti-recursion safeguard), which is why backport PRs land without CI running on them.Test plan
BACKPORT_PATsecret (PAT withreposcope).GITHUB_TOKEN, so behaviour is unchanged for forks / contributors who haven't configured the secret.Closes #655.