Notify merger of incorrectly labeled PRs #1937
Merged
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
carolineechen
requested review from
mthrok,
NicolasHug,
hwangjeff and
nateanl
carolineechen
force-pushed
the
require-pr-labels
branch
from
61be692 to
fe3f2cb
Compare
NicolasHug
approved these changes
Oct 28, 2021
|
Hey @carolineechen! |
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.
To make compilation of release notes easier for future releases, we will start using GitHub labels to label PRs with their associated primary (main) and secondary (subsection) labels. This PR is based on scripts from torchvision (here, here), and will notify the merger if a PR is merged without the proper labels via PR comment.
followups: