FoveaCentral / hit_counter / 27242370731
100%

DEFAULT BRANCH: master
Ran
Jobs 3
Files 2
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 100.0%. Remained the same
27242370731

push

github

web-flow 
build(deps): bump qltysh/qlty-action from 2.2.0 to 2.2.1 (#156)

Bumps [qltysh/qlty-action](https://github.com/qltysh/qlty-action) from
2.2.0 to 2.2.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/qltysh/qlty-action/releases">qltysh/qlty-action's
releases</a>.</em></p>
<blockquote>
<h2>v2.2.1</h2>
<ul>
<li>Bump action runtime to node24</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/qltysh/qlty-action/blob/main/CHANGELOG.md">qltysh/qlty-action's
changelog</a>.</em></p>
<blockquote>
<h1>Changelog</h1>
<h2>v2.2.1 (2026-06-02)</h2>
<ul>
<li>Bump action runtime to node24</li>
</ul>
<h2>v2.2.0 (2025-08-11)</h2>
<ul>
<li>Testing release process (no changes)</li>
</ul>
<h2>v2.1.0 (2025-08-08)</h2>
<h3>New</h3>
<ul>
<li>support &quot;dry-run&quot; option for command
<code>complete</code></li>
</ul>
<h3>Improved</h3>
<ul>
<li>Use log level &quot;error&quot; instead of &quot;warning&quot; when
a catastrophic error occurs but &quot;skip-errors&quot; is true</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Ignore &quot;validate&quot; option when command is
&quot;complete&quot; (otherwise errors with invalid option)</li>
</ul>
<h2>v2.0.0 (2025-08-05)</h2>
<p>This release mirrors the breaking change we introduced in the qlty
CLI proper: we now validate coverage data by default instead of
uploading coverage data to qlty that qlty cannot use. Now you must opt
out of this behavior whereas previously opt in.</p>
<p>What This Means for You:</p>
<ul>
<li>If coverage reporting is working as expected, you'll experience no
impact. If you're uploading valid reports and seeing directory and
file-level coverage metrics in Qlty, you don't need to do anything. (If
your reports include mismatched paths, you'll see specific path errors
listed within your CI output)</li>
<li>Potential CI Build Failures: Once this change is implemented, if
your current CI/CD pipeline uploads a ... (continued)

51 of 51 relevant lines covered (100.0%)

26.0 hits per line

Jobs
ID Job ID Ran Files Coverage
1 27242370731.1 4
100.0
 GitHub Action Run
2 27242370731.2 4
100.0
 GitHub Action Run
3 27242370731.3 4
100.0
 GitHub Action Run
Source Files on build 27242370731