-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DangerJS: Require either 'patch:no', 'patch:yes' or 'patch:done' label #23358
Conversation
a8d8c33
to
8663fe9
Compare
8663fe9
to
efffec8
Compare
Shouldn't this be patched? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@valentinpalkovic I've added the changes to the release tooling that I think are necessary.
I've also changed the danger logic slightly, to allow "patch:done" with "patch:yes" or "patch:no". Essentially we don't remove "patch:yes" when adding "patch:done", I just think we want to ensure that there is always one of either "patch:yes" and "patch:no", ignoring "patch:done".
…patch-label DangerJS: Require either 'patch:no', 'patch:yes' or 'patch:done' label (cherry picked from commit e1350e2)
Closes N/A
What I did
Often the "patch" label is forgotten. This PR changes Danger.js to always enforce setting either a "patch:yes", "patch:no" or "patch:done" label.
Checklist
MIGRATION.MD
Maintainers
make sure to add the
ci:merged
orci:daily
GH label to it.["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]