chore: fix labeler #6692
Merged
chore: fix labeler #6692
Conversation
This file contains 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.
Currently, labeler doesn't work on PRs made from forks, meaning that any community contributions will not have labels. This issue is caused by how the
pull_requesttrigger works.Some time ago, GitHub added a new
pull_request_targettrigger that can safely run Actions against forks, assuming proper configuration.I updated the workflow to match the example from the official GitHub's actions/labeler repository.
You should not use this trigger for other Actions unless you are absolutely sure it's safe. Otherwise, you can leak the
GITHUB_TOKEN. Refer to the pull_request_target documentation for more information.