-
-
Notifications
You must be signed in to change notification settings - Fork 391
Update contributing.md #5213
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
Update contributing.md #5213
Conversation
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.
Nice.
I think you should keep the notice stating that two or more team reviews needs to pass in order for the pull request to be merged. |
That may have been removed by mistake, I was intending to move it to the end section on merging - I'll check the file itself. Edit: nevermind it was merged into the final section :) |
I think you should include a note stating that they don't have to keep the pull request up to date with the master unless it has conflicts. We'll update to master before merging. This helps the developer cherry-picking if we have to port it to other versions to avoid commit searching. |
Would you prefer that here or in the code conventions file? |
Here, it's this discussion. |
Description
Improvements to the code of conduct.
Adds details about what to expect during the review phase, and clears up some old information.