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

joaoh82 / rust_sqlite / 25712135265
69%

Build:
DEFAULT BRANCH: main
Ran 12 May 2026 03:53AM UTC
Jobs 1
Files 61
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

12 May 2026 03:48AM UTC coverage: 68.857%. Remained the same
25712135265

push

github

web-flow
chore(release): fix bump-version.sh commit-message hint + untrack accidental worktree gitlinks (#135)

* chore: untrack accidental .claude/worktrees/ gitlinks + add to .gitignore

The v0.10.0 release commit (937f8b4) captured 8 worktree directories
as gitlinks (mode 160000) because `scripts/bump-version.sh` ran
`git add -A` while the per-phase worktrees were live in
.claude/worktrees/. They aren't real submodules — no `.gitmodules`,
no remote — just orphan gitlink references to commits on the
now-deleted `worktree-phase-*` branches.

Removing the gitlink entries from the index now that the worktrees
have been cleaned up. Adding .claude/worktrees/ to .gitignore so the
next round of phase worktrees doesn't repeat the issue.

Not rewriting v0.10.0's history — the release tag is already
published, and the orphan gitlinks there don't break anything for
consumers (no .gitmodules → git won't try to fetch them on clone).
Forward state is clean from this commit on.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(release): bump-version.sh prints the workflow-expected commit message

Followup from the v0.10.0 release misfire. `scripts/bump-version.sh`
correctly bumps all 11 manifests but doesn't tell the user what to do
next, so a freshly-run script + a manual `git commit -m "chore(release):
bump to <V>"` is a natural shape that silently skips the publish
pipeline (the release workflow's detect regex is
  ^release: v[0-9]+\.[0-9]+\.[0-9]+$
and rejects everything else).

The release-pr.yml workflow path (the "happy" path) already emits the
right commit message; this fix is for the manual-fallback path that the
v0.10.0 release used.

- Print the exact `git commit -am 'release: v<V>'` line.
- Print the recovery command (`gh workflow run release.yml -f
  version=<V>`) for cases when the wrong commit message has already
  been pushed.

Also includes the .claude/worktrees/ gitlink cleanup that was an
unrelated side-effect of the v0.10.0 ... (continued)

11148 of 16190 relevant lines covered (68.86%)

1.24 hits per line

Jobs
ID Job ID Ran Files Coverage
1 25712135265.1 12 May 2026 03:53AM UTC 61
68.86
GitHub Action Run
Source Files on build 25712135265
  • Tree
  • List 61
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • 5f3c865f on github
  • Prev Build on main (#25685215370)
  • Next Build on main (#25713217013)
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