vbrandl/hoc
1
0
Fork 0
Code Issues 1 Pull Requests Actions Projects Releases Wiki Activity

Fix HTML syntax errors

Browse Source
This commit is contained in:
Valentin Brandl 2019-04-17 21:53:43 +02:00
parent 254351e391
commit 5fea37961b
No known key found for this signature in database
GPG Key ID: 30D341DD34118D7D
1 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
static/index.html
View File

@ -10,48 +10,44 @@
<h1>Hits-of-Code Badges</h1> <h1>Hits-of-Code Badges</h1>
<div> <div>
<p>
This API offers badges for the Hits-of-Code metric for your repositories. This metric was proposed by This API offers badges for the Hits-of-Code metric for your repositories. This metric was proposed by
<a href="https://www.yegor256.com/">Yegor Bugayenko</a> as an <a href="https://www.yegor256.com/">Yegor Bugayenko</a> as an
<a href="https://www.yegor256.com/2014/11/14/hits-of-code.html">alternative to Lines-of-Code</a>. <a href="https://www.yegor256.com/2014/11/14/hits-of-code.html">alternative to Lines-of-Code</a>.
</div> </p>
<p /> <p>
Instead of counting the number of existing lines in a codebase, the number of modified lines is counted. That way, the
<div>
Instead of counting the number of existing lines in a codebase, the number of modified lines is counted. That way, the
metric can only grow and never shrink. While this metric still cannot give any information about the code quality, it metric can only grow and never shrink. While this metric still cannot give any information about the code quality, it
gives an overview about the amount of work put into a codebase. gives an overview about the amount of work put into a codebase.
</div> </p>
<p />
<div>
<p> <p>
There is a <a href="https://github.com/yegor256/hoc/">command-line tool</a> to calculate the HoC of a repository, but There is a <a href="https://github.com/yegor256/hoc/">command-line tool</a> to calculate the HoC of a repository, but
some people might want a nice badge to put in their README, that's why I implemented this API. Currently the API can be some people might want a nice badge to put in their README, that's why I implemented this API. Currently the API can be
used for GitHub, GitLab and Bitbucket repositories. Just put the following code in your README: used for GitHub, GitLab and Bitbucket repositories. Just put the following code in your README:
</p>
<pre> <pre>
![Hits-of-Code](https://hoc.oldsql.cc/&lt;service&gt;/&lt;user&gt;/&lt;repo&gt;) ![Hits-of-Code](https://hoc.oldsql.cc/&lt;service&gt;/&lt;user&gt;/&lt;repo&gt;)
</pre> </pre>
</p>
<p> <p>
where <code>&lt;service&gt;</code> is one of <code>github</code>, <code>gitlab</code> or <code>bitbucket</code>. So the where <code>&lt;service&gt;</code> is one of <code>github</code>, <code>gitlab</code> or <code>bitbucket</code>. So the
following Markdown following Markdown
</p>
<pre> <pre>
![Hits-of-Code](https://hoc.oldsql.cc/github/vbrandl/elm-chess) ![Hits-of-Code](https://hoc.oldsql.cc/github/vbrandl/elm-chess)
</pre> </pre>
</p>
<p> <p>
would render this badge: would render this badge:
</p>
<pre> <pre>
<img src="https://hoc.oldsql.cc/github/vbrandl/elm-chess" /> <img src="https://hoc.oldsql.cc/github/vbrandl/elm-chess" />
</pre> </pre>
</p>
</div> </div>
<h2>Source Code</h2> <h2>Source Code</h2>