[Admin] Lower pull request approval requirement to 1
See original GitHub issueHi @node-fetch/core,
-
Per @jimmywarting’s request, I will consider lowering our merge approval count from 2 to 1 in the coming week.
-
Given the number of pending changes and our team member schedule, I believe this will speed up
3.0
development considerably. -
There are definitely some risk involved; as an alternative, I am open to recruiting more active reviewers.
-
If you have any other suggestions or concerns, please feel free to voice it here.
-
If you support the move to lower approval requirement, please leave your vote here so we know 😃
Thx and have a nice day.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:15 (3 by maintainers)
Top Results From Across the Web
On GitHub, allow approving your own PR ... - Stack Overflow
All users must have their pull requests approved but admins may bypass this requirement and merge their own pull requests. I'm having trouble ......
Read more >Merge request approval rules - GitLab Docs
Approval rules define how many approvals a merge request must receive before it can be merged, and which users should do the approving....
Read more >Git branch policies and settings - Azure Repos | Microsoft Learn
A branch that has required policies configured can't be deleted, ... Select Require at least one approval on the last iteration to require...
Read more >Suggest or require checks before a merge | Bitbucket Cloud
Add branch permissions and merge checks to the develop branch · Select Minimum number of approvals and select 2 from the dropdown. ·...
Read more >Ensure GitHub pull requests have at least 2 approvals
In GitHub, repository administrators can require that all pull requests receive a specific number of approving reviews before someone merges the pull request...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @jimmywarting,
If you are looking for admin access to this repo to setup some automation stuffs, please ping @Richienb and @xxczaki directly to setup a role for it. I wasn’t involved in the node-fetch org’s role settings, it would be better if they are involved.
Given current input I have changed required reviewer count to 1, to get the balls rolling on PRs.
Thx.
Ideally, the amount of reviewers should not be constrained by a number we set and forget, but instead by common sense and pure logic. Following the same threshold for all pull requests doesn’t make sense since some can have a bigger impact than others.
However, having 1 as a minimum requires at least 1 other person to take a took which is fine in most circumstances though we should still internalise the fact that we should be waiting for approvals as needed rather than to just satisfy the quota.