CI: fix pr-labeler permissions for external contributions - #87
Merged
Merged
Conversation
Maximus7474
marked this pull request as draft
September 16, 2026 20:35
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.
Description
This PR fixes an issue encountered on #86 where the labeling workflow was unable to run its course and set the relevant labels on PRs from external forks. The changes made on this branch resolve the issue by:
pull_requesttrigger withpull_request_target- allowing the workflow to run in the context of the base repository, which carries write permissions for PR labels.actions/checkoutand localgit logcommands in the commit inspection job with an API call viaactions/github-script- fetching commit messages securely without checking out untrusted fork code.Generative AI Disclosure
Note
Be honest—using GenAI does not penalize your PR, but failing to declare its use may result in the PR not being considered.
(If yes, please briefly describe what tools were used and for what purpose below):
Tests
Additional Notes