-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 template: link to contribution guide #7314
Conversation
Signed-off-by: Shlomi Noach <[email protected]>
.github/pull_request_template.md
Outdated
@@ -1,3 +1,8 @@ | |||
<!-- | |||
How to contribute: https://vitess.io/docs/contributing/ | |||
We’re looking forward to any contribution! Before you start larger contributions, make sure to reach out first and discuss your plans with us. |
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.
us
should link somewhere useful. (I know the doc on the website has the same language and the same problem).
How about linking it to the #developers slack channel?
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 that "us" is vague. This line was copied from https://vitess.io/docs/contributing/ by way of TL;DR. I'm not sure we want to ask people to discuss all contributions on #developers . We should rather encourage them to open an issue. What do you think?
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.
Yes! Let us ask them to create an issue to document the feature, and if they have a proposal it can be marked as an RFC.
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.
Updated.
Signed-off-by: Shlomi Noach <[email protected]>
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.
👍
Description
As discussed in an internal meeting, we see many contributions that are not linked with an existing issue or a prior discussion.
This PR updated th epull request template to first and foremost ask the submitter to read the Contributing guide on the Vitess docs.
Checklist