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

BCR PR reviewer: add support for a "do_not_notify" field #2037

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

Wyverald
Copy link
Member

@Wyverald Wyverald commented Sep 17, 2024

A maintainer can request to not be notified by new PRs by setting "do_not_notify": true. In this case, they can still approve the PR and have it count, but they won't be pinged.

This helps in situations like protobuf's release rotation, which has a lot of people but ideally only the releaser should be notified and be able to approve the PR. It's rather hard to support a "rotating" maintainer model, though. Thus we compromise by adding everyone from that rotation as a "do-not-notify" maintainer, and asking the releaser to watch out for the PR manually as a release step.

cc @zhangskz

A maintainer can request to not be notified by new PRs by setting  `"doNotNotify": true`. In this case, they can still approve the PR and have it count, but they won't be pinged.

This helps in situations like protobuf's release rotation, which has a lot of people but ideally only the releaser should be notified and be able to approve the PR. It's rather hard to support a "rotating" maintainer model, though. Thus we compromise by adding everyone from that rotation as a "do-not-notify" maintainer, and asking the releaser to watch out for the PR manually as a release step.
metadata.json already has the field "yanked_versions" using lower snake case, so I updated this field to follow suit.
@Wyverald Wyverald changed the title BCR PR reviewer: add support for a "doNotNotify" field BCR PR reviewer: add support for a "do_not_notify" field Sep 17, 2024
Copy link
Member

@meteorcloudy meteorcloudy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@meteorcloudy meteorcloudy merged commit 2997e58 into master Sep 18, 2024
7 checks passed
@meteorcloudy meteorcloudy deleted the Wyverald-patch-1 branch September 18, 2024 13:07
Wyverald added a commit to bazelbuild/bazel-central-registry that referenced this pull request Sep 18, 2024
See bazelbuild/continuous-integration#2037. This PR updates the workflows to include that change, and the schema of metadata.json to add the new "do_not_notify" field.
Wyverald added a commit to bazelbuild/bazel-central-registry that referenced this pull request Sep 18, 2024
See bazelbuild/continuous-integration#2037. This
PR updates the workflows to include that change, and the schema of
metadata.json to add the new "do_not_notify" field.

cc @zhangskz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants