bleedingdeacons / link / 33969166189
92%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 11
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: 95.17%. Remained the same
33969166189

push

github

web-flow 
fix: rebase and retry the version push instead of losing the release

A bare `git push` here fails outright when main has moved between the
job's checkout and this line, and it took a real release with it on
2026-09-05: a merge landed sixteen seconds before the push, git refused
the non-fast-forward, and the run died at "Commit the new version" with
every gate already green. Nothing was broken and nothing was published;
the version was simply lost, and the next release skipped a number to
catch up.

The concurrency group above serialises this job against itself, so the
race is never two version jobs. It is a person merging while one is in
flight, which no amount of job-level concurrency can prevent — the other
writer is not a job.

Rebasing is safe for the version this job computed. The bump is derived
from the commit range the run was triggered for, and commits that arrive
meanwhile are not in that range: they get their own run and their own
bump. Landing this commit on top of them skips nothing and
double-counts nothing.

A conflict is deliberately not retried. The only way to conflict here is
another writer touching the same version line, which the concurrency
group already rules out for this job, so it means something genuinely
unexpected — better to fail loudly than resolve it blind. The rebase is
aborted first so the working tree is not left mid-rebase.

Verified against a simulated race rather than by inspection, in two
throwaway repos:

  - a merge lands first, then the job pushes: attempt 1 rejected, rebase,
    attempt 2 succeeds. The version commit ends up on top of the merge,
    the version lands, and the other writer's change survives.
  - both touch the version line: rebase fails, the step exits 1, no
    rebase is left in progress, and origin is untouched.

729 of 766 relevant lines covered (95.17%)

11.27 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33969166189.1 11
95.17
GitHub Action Run
Source Files on build 33969166189