You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
You just made a video about contributing to open source, but not liking the quality or style of pull requests.
Describe the solution you'd like
The GitHub answer to that is to create a CONTRIBUTING.md file that describes how to properly and ideally contribute to your repo. This might include things like "don't make huge changes", "do make a small, specific changes", "Include a cover lever with your PR to describe what you've done", etc.
Also, consider creating a STYLEGUIDE.md file, also in the root of the repo. This will include things like: tabs vs spaces, PascalCase vs camelCase, file naming standards, comment style (e.g. "#" vs "/* */", etc). There is not a formal spec for what is in a repo style guide, so just include the formatting and styling things that you care about.
None. This is for everyone's benefit and it is the industry standard.
Additional context
Adding this communication is a way that you can clearly convey how you would like to see pull requests. Or, if you get a low quality pull request, then you can point the contributor to these files for correction.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
You just made a video about contributing to open source, but not liking the quality or style of pull requests.
Describe the solution you'd like
The GitHub answer to that is to create a
CONTRIBUTING.md
file that describes how to properly and ideally contribute to your repo. This might include things like "don't make huge changes", "do make a small, specific changes", "Include a cover lever with your PR to describe what you've done", etc.Also, consider creating a
STYLEGUIDE.md
file, also in the root of the repo. This will include things like: tabs vs spaces, PascalCase vs camelCase, file naming standards, comment style (e.g. "#" vs "/* */", etc). There is not a formal spec for what is in a repo style guide, so just include the formatting and styling things that you care about.For
CONTRIBUTING.md
see:For
STYLEGUIDE.md
see:Describe alternatives you've considered
None. This is for everyone's benefit and it is the industry standard.
Additional context
Adding this communication is a way that you can clearly convey how you would like to see pull requests. Or, if you get a low quality pull request, then you can point the contributor to these files for correction.
The text was updated successfully, but these errors were encountered: