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

Adding a Template to help guide new PRs. #819

Merged
merged 2 commits into from
Oct 23, 2017
Merged

Conversation

marstr
Copy link
Member

@marstr marstr commented Oct 23, 2017

There are a lot of submissions to the master branch, which will get
immediately released to folks using go get for that reason, we want to
always make sure that master stays in release quality.

There are a lot of submissions to the `master` branch, which will get
immediately released to folks using `go get` for that reason, we want to
always make sure that `master` stays in release quality.
@marstr marstr self-assigned this Oct 23, 2017
@jhendrixMSFT
Copy link
Member

@marstr How about including that the PR links to the issue it fixes and that the change description contains an adequate summary of the fix? So many times we get PRs with very little context.

@marstr
Copy link
Member Author

marstr commented Oct 23, 2017

Change made, @jhendrixMSFT :)

@marstr marstr merged commit f7bb4db into Azure:master Oct 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants