<h1>Contributing<aclass="headerlink"href="#contributing"title="Permalink to this headline">¶</a></h1>
<p>Contributions are welcome, and they are greatly appreciated! Every
little bit helps, and credit will always be given.</p>
<p>You can contribute in many ways:</p>
<divclass="section"id="types-of-contributions">
<h2>Types of Contributions<aclass="headerlink"href="#types-of-contributions"title="Permalink to this headline">¶</a></h2>
<divclass="section"id="report-bugs">
<h3>Report Bugs<aclass="headerlink"href="#report-bugs"title="Permalink to this headline">¶</a></h3>
<p>Report bugs at <aclass="reference external"href="https://github.com/elfsternberg/git_lint/issues">https://github.com/elfsternberg/git_lint/issues</a>.</p>
<p>If you are reporting a bug, please include:</p>
<ulclass="simple">
<li>Your operating system name and version.</li>
<li>Any details about your local setup that might be helpful in troubleshooting.</li>
<li>Detailed steps to reproduce the bug.</li>
</ul>
</div>
<divclass="section"id="fix-bugs">
<h3>Fix Bugs<aclass="headerlink"href="#fix-bugs"title="Permalink to this headline">¶</a></h3>
<p>Look through the GitHub issues for bugs. Anything tagged with “bug”
is open to whoever wants to implement it.</p>
</div>
<divclass="section"id="implement-features">
<h3>Implement Features<aclass="headerlink"href="#implement-features"title="Permalink to this headline">¶</a></h3>
<p>Look through the GitHub issues for features. Anything tagged with “feature”
is open to whoever wants to implement it.</p>
</div>
<divclass="section"id="write-documentation">
<h3>Write Documentation<aclass="headerlink"href="#write-documentation"title="Permalink to this headline">¶</a></h3>
<p>Git Lint could always use more documentation, whether as part of the
official Git Lint docs, in docstrings, or even on the web in blog posts,
articles, and such.</p>
</div>
<divclass="section"id="submit-feedback">
<h3>Submit Feedback<aclass="headerlink"href="#submit-feedback"title="Permalink to this headline">¶</a></h3>
<p>The best way to send feedback is to file an issue at <aclass="reference external"href="https://github.com/elfsternberg/git_lint/issues">https://github.com/elfsternberg/git_lint/issues</a>.</p>
<p>If you are proposing a feature:</p>
<ulclass="simple">
<li>Explain in detail how it would work.</li>
<li>Keep the scope as narrow as possible, to make it easier to implement.</li>
<li>Remember that this is a volunteer-driven project, and that contributions
are welcome :)</li>
</ul>
</div>
</div>
<divclass="section"id="get-started">
<h2>Get Started!<aclass="headerlink"href="#get-started"title="Permalink to this headline">¶</a></h2>
<p>Ready to contribute? Here’s how to set up <cite>git_lint</cite> for local development.</p>
<olclass="arabic">
<li><pclass="first">Fork the <cite>git_lint</cite> repo on GitHub.</p>
<li><pclass="first">Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:</p>
<li><pclass="first">When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:</p>