-
Notifications
You must be signed in to change notification settings - Fork 110
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
Add CONTRIBUTING.md #36
Comments
@GaryJones : : Do you have any personal preference or best practice to share as to whether this should be a standalone |
Since GitHub adds a big yellow banner for New Issues / new PRs when it detects a ## Contributing
See the [guidelines for contributions](CONTRIBUTING.md). ... in the README. The advantage to putting |
@GaryJones : : I had no idea that GitHub added a yellow banner based on the existence of that file. That's pretty fantastic! @tommcfarlin suggested the same linking to the Thanks for the tips! |
@GaryJones : : Just wanted to say thanks again for all you help on this and some of the other prodding on other issues. The CONTRIBUTING.md file also points out why (I believe) simply editing the XML file directly is not possible. If that sounds bogus to you, then let me know if you have any other tips / tricks. |
The description in Wait - @tommcfarlin - shy?! ;-) |
@GaryJones : : As to your question on the code review... I would love to fix the root cause and one would think it should be solvable. I appreciate you taking the time to find that trac issue and mention WP Test on it. |
Add a CONTRIBUTING.md file, and link to it from the readme, so potential contributors can be guided as to how they can make changes for PRs. It should cover how to export the updated XML file.
The text was updated successfully, but these errors were encountered: