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

When there is no branch protected, the reviews of those who have code write permission should be consider as official #10624

Open
lunny opened this issue Mar 6, 2020 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented pr/breaking Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it! type/enhancement An improvement of existing functionality

Comments

@lunny
Copy link
Member

lunny commented Mar 6, 2020

As above.

If no branch protected, then no official review. Should we change that?

@lunny lunny added the type/bug label Mar 6, 2020
@lunny lunny added this to the 1.11.3 milestone Mar 6, 2020
@lunny lunny removed the type/bug label Mar 6, 2020
@lunny lunny removed this from the 1.11.3 milestone Mar 6, 2020
@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Mar 6, 2020
@guillep2k
Copy link
Member

I thought it was always official unless there's a whitelist and the user is not in it. Maybe we've missed that case for unprotected branches?

@lunny
Copy link
Member Author

lunny commented Mar 6, 2020

@guillep2k see https://github.com/go-gitea/gitea/blob/master/models/review.go#L195 , when there is no branch protected, no reviewer will be consider as official.

@guillep2k
Copy link
Member

As Syndrome said: "if everyone is special, then nobody is special" 😄

I agree, I think those should be "official".

@lunny lunny changed the title Collabrator with write permissions' review should be official When there is no branch protected, the reviews of those who have code write permission should be consider as official Mar 6, 2020
@lunny lunny added pr/breaking Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it! type/enhancement An improvement of existing functionality and removed type/question Issue needs no code to be fixed, only a description on how to fix it yourself. labels Mar 6, 2020
@stale
Copy link

stale bot commented May 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label May 6, 2020
@guillep2k guillep2k added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label May 20, 2020
@stale stale bot removed the issue/stale label May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented pr/breaking Merging this PR means builds will break. Needs a description what exactly breaks, and how to fix it! type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants