-
Notifications
You must be signed in to change notification settings - Fork 441
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
Add community-reviewed label is need to merge #2851
Conversation
I won't be able to review this PR, but as someone who lives on the other side of the planet (well, active in time zones on the other side of the planet), this is much appreciated :) Thanks for all the work you put into this. |
Codecov Report
@@ Coverage Diff @@
## main #2851 +/- ##
=======================================
Coverage 94.03% 94.03%
=======================================
Files 76 76
Lines 16399 16399
=======================================
Hits 15420 15420
Misses 979 979 |
@adeak Thanks. This PR was largely inspired by your "Improving review habit" thread. |
As a matter of course, the Pull Request result is always red before |
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.
Cool! I'm going to approve and see if automerge works after 24 hr.
Whelp. Forgot to add the label as a merge requirement. |
"triage" added as a merge requirement. |
@akaszynski Thanks. |
This reverts commit 5c36c18.
Overview
The PyVista community has grown and also the developer community has grown. Nowadays, pull requests are reviewed from multiple locations around the world. Every time zone in the world should have an equal opportunity to review PyVista's pull request. In other words, reviewers should be granted their chance to review for at least 1 day. However, maintainers, myself included, tend to be aggressive in merging (because we want to improve PyVista quickly!). It is also painful to open an uncommented PullRequest after a day pass even though there is an enable auto-merge.
So I built a system to solve this problem with GitHub Action. This system is divided into two parts.
Community Review: Here the label
community-reviewed
is added one day after the last action in the PullRequest. If someone takes some action, it will wait another day. If someone comments, thecommunity-reviewed
label is removed and ado-not-merge
label is added. This label prevents merging, so please remove it when the discussion is over. You can also add it when you feel a long time discussion is needed.Pull Request Labels: Here we check the labels required for the merge, blocking the merge if they do not meet the criteria. The label
community-reviewed
, which is given if 1. is passed, is a required label.do-not-merge
is a label that must not exist to merge. We also need a required label for release notes. This solves the problem of Fix GitHub Action's expression #2453 .Please review as there may be use cases that I am not anticipating. Reviews are always important!!!
relate to #2245
resolves #2774
Details