Skip to content
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

Merged
merged 3 commits into from
Jul 11, 2023

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Jul 7, 2023

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

  • Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
  • Make sure to add/update documentation regarding your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Maintainers

  • If this PR should be tested against many or all sandboxes,
    make sure to add the ci:merged or ci:daily GH label to it.
  • Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

@valentinpalkovic valentinpalkovic changed the title Require either 'patch' or 'no-patch' label DangerJS: Require either 'patch' or 'no-patch' label Jul 7, 2023
@valentinpalkovic valentinpalkovic added build Internal-facing build tooling & test updates no-patch labels Jul 7, 2023
@valentinpalkovic valentinpalkovic force-pushed the valentin/require-patch-no-patch-label branch from a8d8c33 to 8663fe9 Compare July 7, 2023 12:57
@valentinpalkovic valentinpalkovic changed the title DangerJS: Require either 'patch' or 'no-patch' label DangerJS: Require either 'patch:no', 'patch:yes' or 'patch:done' label Jul 7, 2023
@shilman
Copy link
Member

shilman commented Jul 11, 2023

Shouldn't this be patched?

@valentinpalkovic valentinpalkovic added patch:yes Bugfix & documentation PR that need to be picked to main branch patch:yes and removed patch:no patch:yes Bugfix & documentation PR that need to be picked to main branch labels Jul 11, 2023
Copy link
Contributor

@JReinhold JReinhold left a 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".

@valentinpalkovic valentinpalkovic merged commit e1350e2 into next Jul 11, 2023
@valentinpalkovic valentinpalkovic deleted the valentin/require-patch-no-patch-label branch July 11, 2023 13:47
@github-actions github-actions bot mentioned this pull request Jul 11, 2023
9 tasks
JReinhold pushed a commit that referenced this pull request Jul 11, 2023
…patch-label

DangerJS: Require either 'patch:no', 'patch:yes' or 'patch:done' label
(cherry picked from commit e1350e2)
@github-actions github-actions bot mentioned this pull request Jul 11, 2023
10 tasks
@github-actions github-actions bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Internal-facing build tooling & test updates patch:done Patch/release PRs already cherry-picked to main/release branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants