667
edits
Changes
→Step 7. Contribute to Another Project
Before you contribute to another project, make sure there is either an existing bug, or file one yourself. Make sure the project owner knows you're working on this issue.
Next, <code>fork</code> and <code>clone</code> their repo. Create a <code>branch</code> for the issue you're fixing, make your changes, <code>add</code>, and <code>commit</code>. Then <code>push</code> your branch to your <code>fork</code>.
Finally, create a [https://help.github.com/articles/about-pull-requests/ Pull Request] for your change. In your Pull Request's description, make sure you use the pattern <code>Fix #...: <desc>...</code> to have GitHub automatically close the associated issue when your Pull Request is merged. For example, if you are working on Issue 14, you might say, <code>Fix #14: add md5 unit test</code>. Also include a useful discussion of what you've done, how to test it, etc.
==Step 7. Code Review==
