<dd>Group reports by linter first as they appear in the config file [default]</dd>
<dt><strong>-f, –byfile</strong></dt>
<dd>Group reports by file first, linter second</dd>
<dt><strong>-d, –dryrun</strong></dt>
<dd>Report what git-lint would do, but don’t actually do anything.</dd>
<dt><strong>-q, –quiet</strong></dt>
<dd>Produce a short report of file that failed to pass.</dd>
<dt><strong>-h, –help</strong></dt>
<dd>Print a short help message</dd>
<dt><strong>-V, –verbose</strong></dt>
<dd>Print a slightly more verbose long report</dd>
<dt><strong>-v, –version</strong></dt>
<dd>Print version information</dd>
</dl>
</div>
<divclass="section"id="output">
<h2>OUTPUT<aclass="headerlink"href="#output"title="Permalink to this headline">¶</a></h2>
<p>By default, the output is that of all the linters specified, in the
order in which they appear in the configuration file, followed by
every file specified, sorted ASCIIbetically. This order can be
flipped (files first, then linters) with the <codeclass="docutils literal"><spanclass="pre">--byfiles</span></code> option.</p>
<p><codeclass="docutils literal"><spanclass="pre">git</span><spanclass="pre">lint</span></code> returns the maximal error code if any linters fail a
pass, or zero if they all succeed.</p>
</div>
<divclass="section"id="configuration">
<h2>CONFIGURATION<aclass="headerlink"href="#configuration"title="Permalink to this headline">¶</a></h2>
<p><codeclass="docutils literal"><spanclass="pre">git</span><spanclass="pre">lint</span></code> uses a standard INI-style configuration file. Aside from the
DEFAULT section, the name of each section is an alphanumeric token name for
a linter, followed by configuration details for that linter. Standard details
are:</p>
<ulclass="simple">
<li>output - Text to print before running a linter.</li>
<li>command - The actual command to run, minus the file path</li>
<li>match - A comma-separated list of extensions to match against the linter</li>
<li>print - If true, will prefix each line of output from the linter with the filename</li>
<li>condition - if “error”, the return code of the linter is the status of the pass. If “output,” any output will result in a failure.</li>
<li>comment - Text to include when running the <codeclass="docutils literal"><spanclass="pre">--linters</span></code> option</li>