-
Notifications
You must be signed in to change notification settings - Fork 688
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
Pull Request Etiquette and Best Practices #5953
base: dev
Are you sure you want to change the base?
Conversation
Recreated PR as I mistakenly left the default branch name which didn't trigger CI. |
Team review: We do not agree on a few of the points being suggested here. We should have a team discussion on these first. |
Yes, I already had this in the team meeting agenda. If you can share your concern here, please do. |
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.
Proposing changes based on team meeting
Co-authored-by: Nikolche Kolev <[email protected]>
Not stale, just awaiting approvals |
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.
I think people may want to rereview in a team meeting, but LGTM.
Merging is blocked because @aortiz-msft would like to discuss this again in the 9/12 Team Meeting. |
Bump #5953 (comment) |
Bump #5953 (comment) |
Discussed in Team Meeting 9/12. Let me know if there are suggested changes to make here. |
Bump #5953 (comment) |
I'd merge this :) 5 approvals on latest (including a double one by me :D ) |
Sure! @aortiz-msft sound good? |
This PR has been automatically marked as stale because it has no activity for 7 days. It will be closed if no further activity occurs within another 7 days of this comment. If it is closed, you may reopen it anytime when you're ready again, as long as you don't delete the branch. |
Copied directly from the Azure SDK team's repo. I read their contributing document recently and thought it seemed appropriate that they call out PR Review etiquette. We have been wanting to improve our PR etiquette for years and I believe writing down guidelines is a step to achieving common understanding.