workflows/pr-severity: use pull_request_target for fork PRs#10527
Merged
Roasbeef merged 1 commit intolightningnetwork:masterfrom Jan 28, 2026
Merged
workflows/pr-severity: use pull_request_target for fork PRs#10527Roasbeef merged 1 commit intolightningnetwork:masterfrom
Roasbeef merged 1 commit intolightningnetwork:masterfrom
Conversation
Switch from pull_request to pull_request_target to allow the workflow to run on PRs from forks. The pull_request trigger runs in the fork's context which cannot access repository secrets. This is safe because the workflow only reads PR metadata via the GitHub API (changed files, labels) and doesn't checkout or execute any code from the PR itself.
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
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.
Switch from pull_request to pull_request_target to allow the workflow to run on PRs from forks. The pull_request trigger runs in the fork's context which cannot access repository secrets.
This is safe because the workflow only reads PR metadata via the GitHub API (changed files, labels) and doesn't checkout or execute any code from the PR itself.
We'll now this works if after the merge, we can add the
reclassifylabel and it'll run the bot.