-
Notifications
You must be signed in to change notification settings - Fork 160
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
docs: Update Acceptance policy #4053
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.
two small nits
@@ -23,6 +23,11 @@ These things will make a PR more likely to be accepted: | |||
- tests for old code! | |||
- new code and tests follow the conventions in old code and tests | |||
- a good commit message (see below) | |||
- all code must abide by [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments) | |||
- names should abide by [What's in a name](https://talks.golang.org/2014/names.slide#1) | |||
- code must build on both Linux and Darwin, via plain `go build` |
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.
That's a tricky one to enforce. It makes sense, but as a random person if I try to join to contribute that may make some uncertainties as I have no mac where I can test and build.
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.
Agreed, this is not meant to be a strict/hard requirement but rather an acknowledgment that a simple go build
should be sufficient.
What changed?
Updated Acceptance policy.
Why was this change made?
To make PR requirements more explicit.
How was this change implemented?
N/A
How did you validate the change?
N/A
Release notes
N/A
Documentation Changes
N/A