<p>If there are no failures, you're good to go.</p>
</li>
<li>
<p><strong><ahref="https://help.github.com/articles/fork-a-repo/">Fork the repo</a> so you can change it locally.</strong> Please make your
changes in a separate <ahref="https://www.atlassian.com/git/tutorials/comparing-workflows/centralized-workflow">feature branches</a> to make things a little easier on
me.</p>
</li>
<li>
<p><strong>Change the code.</strong> Please follow the style of the surrounding code. That
basically means <code>camelCase</code> names, <code>{</code> on the next line, keep within 80
columns, and two spaces of indentation. If you see places where the existing
code is inconsistent, let me know.</p>
</li>
<li>
<p><strong>Write some tests for your new functionality.</strong> They live under <code>test/</code>.
Take a look at some existing tests to get an idea of how to define
expectations.</p>
</li>
<li>
<p><strong>Make sure the tests all pass, both the old ones and your new ones.</strong></p>
</li>
<li>
<p><strong>Add your name and email to the <ahref="https://github.com/munificent/wren/tree/master/AUTHORS">AUTHORS</a> file if you haven't already.</strong></p>
</li>
<li>
<p><strong>Send a <ahref="https://github.com/munificent/wren/pulls">pull request</a>.</strong> Pat yourself on the back for contributing to a
fun open source project! I'll take it from here and hopefully we'll get it
landed smoothly.</p>
</li>
</ol>
<p>If at any point you have questions, feel free to <ahref="https://github.com/munificent/wren/issues">file an issue</a> or
email me (<code>robert</code> at <code>stuffwithstuff.com</code>). <em>Thank you!</em></p>
<p>Wren lives <ahref="https://github.com/munificent/wren">on GitHub</a>— Made with ❤ by <ahref="http://journal.stuffwithstuff.com/">Bob Nystrom</a>.</p>