Sha256: 010c6207649ee2f90dd92da11f39a9d3f459258f3fb279c230489ee7d049f80e
Contents?: true
Size: 1.46 KB
Versions: 11
Compression:
Stored size: 1.46 KB
Contents
<h1 id='contribute'>Contribute</h1> <p>Want to advance Barometer? Help out by contributing!</p> <h2 id='find_a_bug'>Find a bug?</h2> <p>Add it to GitHub by <a href='http://github.com/attack/barometer/issues'>creating a new issue</a>. Be sure to include all relevant information, like the versions of Barometer and Ruby you’re using. A <a href='http://gist.github.com/'>gist</a> of the code that caused the issue as well as any error messages are also very helpful.</p> <h2 id='have_a_patch'>Have a patch?</h2> <p>Bugs and feature requests that include patches are much more likely to get attention. Here are some guidelines that will help ensure your patch can be applied as quickly as possible:</p> <ol> <li> <p><strong>Use <a href='http://git-scm.com'>Git</a> and <a href='http://github.com'>GitHub</a>:</strong> The easiest way to get setup is to fork the <a href='http://github.com/attack/barometer/'>attack/barometer repo</a>. </p> </li> <li> <p><strong>Write spec tests:</strong> If you add or modify functionality, it must include spec tests.</p> </li> <li> <p><strong>Mind the <code>README</code>:</strong> If the patch adds or modifies a major feature, modify the <code>README.rdoc</code> file to reflect that.</p> </li> <li> <p><strong>Push it:</strong> Once you’re ready, push your changes to a topic branch and add a note to the ticket with the URL to your branch. Or, say something like, “you can find the patch on johndoe/foobranch”.</p> </li> </ol>
Version data entries
11 entries across 11 versions & 2 rubygems