-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Approvals at Branch Protection #5350
Approvals at Branch Protection #5350
Conversation
Signed-off-by: Jonas Franz <[email protected]>
Signed-off-by: Jonas Franz <[email protected]>
Signed-off-by: Jonas Franz <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #5350 +/- ##
==========================================
- Coverage 37.61% 37.61% -0.01%
==========================================
Files 317 318 +1
Lines 46835 46928 +93
==========================================
+ Hits 17619 17650 +31
- Misses 26712 26770 +58
- Partials 2504 2508 +4
Continue to review full report at Codecov.
|
@JonasFranzDEV any screenshot? |
@lunny fixed your first comment and added screenshots. |
I think this depends on #5132 to have single method that returns latest per-user reviews |
right, blocked by #5132 |
Do we allow merging if there is request for changes? |
@lafriks I'd make this an option which could be toggled on or off in the settings (default not allowing) |
Yes this can be added in other PR as an option |
@lafriks I think @JonasFranzDEV is right, allow merging or not when there is request for changes should be another PR. |
…re/branch-protection-approvals
…sFranzDEV/gitea into feature/branch-protection-approvals Signed-off-by: Jonas Franz <[email protected]> # Conflicts: # models/review_test.go
Signed-off-by: Jonas Franz <[email protected]>
@lunny need your review |
file conflict. |
@lunny File conflicts resolved |
@lunny is this using the function from Review summaries? |
@kolaente yes, I think that's the reason. |
Maybe this could be resolved by #5502 |
Can you verify that? @lunny |
You have to add |
Fixes #5251
This PR adds approvals limitations to branch protection. A pitfall is that it is currently only possible to assign Teams/Users with write permissions to branch protection. I've removed this for teams but not for users.
Screenshots