Fix PR labeler #2486
Merged
Fix PR labeler #2486
Conversation
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.
Description
If someone submits a PR from a forked repository, the labeler would not have write permission to the PR to add labels. As a result, PRs from forked repos are not labeled. This PR fixes this problem.
Related Issue
There is no open issue for this PR.
How Has This Been Tested?
It is not tested because I could not find a way to test this. The labeler reads labeler.yml on the master branch. So, we cannot test if this PR solves the issue until it is merged into master. However, Github documentation is very clear on this problem. In worst case, if anything goes wrong, I can make another PR and revert this change.
Types of changes
Checklist: