-
Notifications
You must be signed in to change notification settings - Fork 199
Contributor docs: write up merge practices #1830
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
Conversation
While the governance doc covers some _rules_, it doesn't catch some of our unwritten conventions. I've written this up in anticipation of adding new peers.
30bc2f4 to
a41c3fe
Compare
jamesnw
left a comment
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.
Thanks for writing this up! It's very helpful.
docs/reviewing.md
Outdated
| If a pull request has been approved and tests are passing, then you can merge it. | ||
| Follow these steps to merge: | ||
|
|
||
| 1. Make sure **you** can merge this pull request. |
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.
A suggested addition-
1. Make sure you **should** merge this pull request.
In general, only merge pull requests you are already familiar with, either as an author or reviewer. Co-authored-by: James Stuckey Weber <jamesnw@gmail.com>
Co-authored-by: James Stuckey Weber <james@oddbird.net>
captainbrosset
left a comment
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.
A few non-blocking comments.
Co-authored-by: Patrick Brosset <patrickbrosset@gmail.com>
While the governance doc covers some rules, it doesn't catch some of our unwritten conventions. I've written this up in anticipation of adding new peers.