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

openSUSE / qem-dashboard / 26881679379 / 1
100%
main: 100%

Build:
DEFAULT BRANCH: main
Ran 03 Jun 2026 11:30AM UTC
Files 33
Run time 2s
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

01 Jun 2026 06:27PM UTC coverage: 100.0%. Remained the same
26881679379.1

push

github

okurz
ci: improve gitlint range detection by verifying commit existence

Motivation
On 'push' events, gitlint was failing with 'fatal: Invalid revision range'
because the 'before' SHA provided by GitHub was not always present in the local
clone (e.g., after force-pushes or rebases). The existing check using
'git rev-parse --verify' was insufficient because it only validates SHA format
for 40-character strings, rather than confirming the commit exists in the
object database.

Design Choices
Replaced 'git rev-parse --verify "$BEFORE"' with 'git cat-file -e "$BEFORE"' in
the checkstyle-npm workflow. Unlike 'rev-parse', 'cat-file -e' explicitly
validates that the object exists in the local repository. If the commit is
missing, the script now correctly falls back to linting only the latest commit.

Benefits
Prevents spurious CI failures on branches with rewritten history while ensuring
new commits are still properly linted.

1797 of 1797 relevant lines covered (100.0%)

8.31 hits per line

Source Files on job 26881679379.1
  • Tree
  • List 33
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 26881679379
  • 6e9fee56 on github
  • Prev Job for on main (#26762660746.1)
  • Next Job for on main (#27018664970.1)
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