-
Notifications
You must be signed in to change notification settings - Fork 193
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
Proposal: Not merging your own PRs without an explicit r+ or lgtm #1110
Comments
👍💯 |
I can take a look for adding a bot and update the documentation, If everyone agrees. |
karlcow
added a commit
to karlcow/webcompat.com
that referenced
this issue
Jul 5, 2016
karlcow
added a commit
to karlcow/webcompat.com
that referenced
this issue
Jul 5, 2016
@magsout for the bot, maybe that should be its own separate issue. I guess it will take a bit longer. |
karlcow
added a commit
to karlcow/webcompat.com
that referenced
this issue
Jul 5, 2016
karlcow
added a commit
to karlcow/webcompat.com
that referenced
this issue
Jul 5, 2016
karlcow
added a commit
to karlcow/webcompat.com
that referenced
this issue
Jul 5, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now the Submission Guidelines mention asking for review explicitly:
https://github.com/webcompat/webcompat.com/blob/master/CONTRIBUTING.md#submission-guidelines
I think we should add a section about not merging your own PR unless the person reviewing has left an explicit "r+" or "lgtm" comment. Possible ways this happens:
(admins should be able to merge w/o r+ or lgtm, in the case of fixing broken builds, etc.)
We should be able to enforce this w/ a bot: https://github.com/blog/2051-protected-branches-and-required-status-checks, but for now we can just trust each other.
Thoughts? @webcompat/core-developers
The text was updated successfully, but these errors were encountered: