2019-04-23 18:19:54 +02:00
|
|
|
@use super::base;
|
2019-04-30 14:20:11 +02:00
|
|
|
@use crate::VersionInfo;
|
2019-04-23 18:19:54 +02:00
|
|
|
|
2019-04-30 14:20:11 +02:00
|
|
|
@(version_info: VersionInfo, domain: &str)
|
2019-04-23 18:19:54 +02:00
|
|
|
|
|
|
|
@:base("Hits-of-Code Badges", "Hits-of-Code Badges", {
|
|
|
|
|
|
|
|
<p>
|
|
|
|
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/2014/11/14/hits-of-code.html">alternative to Lines-of-Code</a>.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
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
|
|
|
|
gives an overview about the amount of work put into a codebase.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
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
|
|
|
|
used for GitHub, GitLab and Bitbucket repositories. Just put the following code in your README:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
2019-04-23 22:50:51 +02:00
|
|
|
[![Hits-of-Code](https://@domain/<service>/<user>/<repo>)](https://@domain/view/<service>/<user>/<repo>)
|
2019-04-23 18:19:54 +02:00
|
|
|
</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
where <code><service></code> is one of <code>github</code>, <code>gitlab</code> or <code>bitbucket</code>. So the
|
|
|
|
following Markdown
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
2019-04-23 22:50:51 +02:00
|
|
|
[![Hits-of-Code](https://@domain/github/vbrandl/hoc)](https://@domain/view/github/vbrandl/hoc)
|
2019-04-23 18:19:54 +02:00
|
|
|
</pre>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
would render this badge:
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<pre>
|
2019-04-23 22:50:51 +02:00
|
|
|
<a href="https://@domain/view/github/vbrandl/hoc"><img src="https://@domain/github/vbrandl/hoc"
|
2019-04-23 18:19:54 +02:00
|
|
|
alt="example badge" /></a>
|
|
|
|
</pre>
|
|
|
|
|
2019-05-04 15:38:00 +02:00
|
|
|
<h2>Badge Generator</h2>
|
|
|
|
|
|
|
|
<form method="post" action="/generate">
|
|
|
|
<select name="service" id="service">
|
|
|
|
<option value="github">GitHub</option>
|
|
|
|
<option value="gitlab">Gitlab</option>
|
|
|
|
<option value="bitbucket">Bitbucket</option>
|
|
|
|
</select>
|
|
|
|
<label>/</label>
|
|
|
|
<input name="user" id="user" type="text" placeholder="user" />
|
|
|
|
<label>/</label>
|
|
|
|
<input name="repo" id="repo" type="text" placeholder="repository" />
|
|
|
|
<button type="submit">Generate</button>
|
|
|
|
</form>
|
|
|
|
|
2019-04-23 18:19:54 +02:00
|
|
|
<h2>Source Code</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
The whole service is licensed under the <a href="https://opensource.org/licenses/MIT">MIT license</a> and the source
|
|
|
|
code <a href="https://github.com/vbrandl/hoc">can be found on GitHub</a>. Feature proposals or pull requests are
|
|
|
|
welcome.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Contact</h2>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
You can reach me via mail: <a href="mailto:mail+hoc@@vbrandl.net">mail+hoc@@vbrandl.net</a> preferably using
|
|
|
|
my <a href="https://mirror.oldsql.cc/key.asc">GPG key</a>
|
|
|
|
(<a href="http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x1FFE431282F4B8CC0A7579167FB009175885FC76">from a
|
|
|
|
keyserver</a>), or by using any other UID from my key.
|
|
|
|
</p>
|
2019-04-30 14:20:11 +02:00
|
|
|
}, version_info)
|