-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Resolve issue #7000 by adding PR size-labeling GitHub Actions workflow #7203
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
Conversation
This size labeling workflow should be a close approximation to what CirqBot currently does via `pr_monitor`. Once in place, it should be possible to remove pr_monitor from the Cirq code base, because the automerge functionality of pr_monitor (which is the other thing that it did) is now implemented using GitHub's merge queues. This basically resolves quantumlib#7000.
Related issue: #6024 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7203 +/- ##
=======================================
Coverage 98.14% 98.14%
=======================================
Files 1100 1100
Lines 96244 96244
=======================================
Hits 94462 94462
Misses 1782 1782 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
.github/workflows/pr-labeler.yaml
Outdated
The size of this pull request exceeds 1000 additions and/or | ||
deletions. Extra large pull requests like this are more difficult | ||
to review, and sometimes their large size signals that they could | ||
be restructured. Please check the following: | ||
|
||
- [ ] Are the git commits in this PR limited to what's needed? Or | ||
is it possible that other commits were included accidentally? | ||
|
||
- [ ] Does this PR only address one issue, feature, problem, or | ||
topic? Or are multiple issues or changes mixed together? | ||
|
||
Sometimes large commits really are needed, and that's okay! | ||
Examples include reformatting code using an automated tool, | ||
refactoring code, and adding generated code. At other times, a | ||
large PR could benefit by reconsidering it in light of the [Small | ||
CLs](https://google.github.io/eng-practices/review/developer/small-cls.html) | ||
principles. |
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.
Let us take this out, the advice can be spammy for experienced developers.
New contributors are less likely to produce an XL PR. Either of those need to
be human-reviewed and we can ask to split such PRs where it makes sense.
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.
Let us take this out, the advice can be spammy for experienced developers. New contributors are less likely to produce an XL PR. Either of those need to be human-reviewed and we can ask to split such PRs where it makes sense.
Yeah, you're right. Taking it out.
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.
LGTM after removing the XL message.
Review comments led to the conclusion that the message is unnecessary and more likely to be annoying than helpfu.
…ib#7203) * Add PR labeler workflow with size labeling (for now) This size labeling workflow should be a close approximation to what CirqBot currently does via `pr_monitor`. Once in place, it should be possible to remove pr_monitor from the Cirq code base, because the automerge functionality of pr_monitor (which is the other thing that it did) is now implemented using GitHub's merge queues. This basically resolves quantumlib#7000. * Remove message for XL changes Review comments led to the conclusion that the message is unnecessary and more likely to be annoying than helpfu.
This workflow adds automatic labeling of sizes of PRs. It's configured to use
the same labels we use in Cirq (e.g.,
size: M
,size: L
, etc.) and thebehavior should be a close approximation to what CirqBot currently does via
pr_monitor
. Once in place, it should then be possible to removepr_monitor
from the Cirq code base, because its automerge functionality (which is the
other thing that it did) is now done using GitHub's merge queues.
This basically resolves #7000 and #6935.