• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FoveaCentral / vaccinesignup / 19251413742
95%

Build:
DEFAULT BRANCH: main
Ran 11 Nov 2025 01:06AM UTC
Jobs 1
Files 10
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

11 Nov 2025 01:05AM UTC coverage: 94.697%. Remained the same
19251413742

push

github

web-flow
build(deps): bump qltysh/qlty-action from 1 to 2 (#608)

Bumps [qltysh/qlty-action](https://github.com/qltysh/qlty-action) from 1
to 2.
<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.0.0</h2>
<p>This release mirrors the breaking change we introduced in the qlty
CLI proper: we now validate coverage data by default instead of
uplpoading 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 report with mismatched paths, your
builds will begin to fail when executing qlty coverage publish.</li>
<li>Quick Fix for Build Failures: If your builds start failing and you
need to get them passing immediately, you can temporarily add validate:
false to the GitHub Action configuration. This will disable validation
and allow your CI build to pass (though your coverage data will remain
broken until you've uploaded a valid report).</li>
</ul>
<p>We believe this change will significantly improve the accuracy and
usability of your coverage data within Qlty. If you have any questions
or require assistance, please don't hesitate to contact our support
team.</p>
<h2>v1.2.0 (2025-08-04)</h2>
<h3>Fixed</h3>
<ul>
<li>Ensure correct commit sha provided from PRs for 'complete' action
(<a
href="https://redirect.github.com/qltysh/qlty-action/issues/125">#125</a>)</li>
<li>More robust error output in face of unknown errors (<a
href="https... (continued)

125 of 132 relevant lines covered (94.7%)

11.86 hits per line

Jobs
ID Job ID Ran Files Coverage
1 19251413742.1 11 Nov 2025 01:06AM UTC 20
94.7
GitHub Action Run
Source Files on build 19251413742
  • Tree
  • List 10
  • Changed 10
  • Source Changed 0
  • Coverage Changed 10
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #19251413742
  • 3cfb7b70 on github
  • Prev Build on main (#19251378774)
  • Next Build on main (#19253651401)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc