fix: Use PAT for rebase workflow to trigger subsequent checks#1001
Merged
mPokornyETM merged 2 commits intomasterfrom Apr 10, 2026
Merged
fix: Use PAT for rebase workflow to trigger subsequent checks#1001mPokornyETM merged 2 commits intomasterfrom
mPokornyETM merged 2 commits intomasterfrom
Conversation
24598b3 to
2b9d3d0
Compare
When using github.token, force-pushes don't trigger other workflows like Jenkins Security Scan. Using a PAT (GH_TOKEN secret) fixes this. Falls back to github.token if secret is not configured. To complete this fix, a repository admin needs to: 1. Create a PAT with 'repo' and 'workflow' scopes 2. Add it as repository secret named GH_TOKEN
3775d37 to
d37cec0
Compare
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
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
Use PAT instead of github.token for the rebase workflow to trigger subsequent CI checks.
Problem
When the rebase workflow force-pushes PR branches, it uses github.token. GitHub does not trigger other workflows (like Jenkins Security Scan) for pushes made with this token - this is a security feature to prevent recursive triggers.
This caused PRs to get stuck because the required Jenkins Security Scan check never ran after rebasing.
Solution
To complete this fix
A repository admin needs to: