|
Ran
|
Jobs
1
|
Files
124
|
Run time
1min
|
Badge
README BADGES
|
push
github
fix(ci): stop deploys from displacing the docs preview cleanup (#391) (#392) A concurrency group holds at most one pending run, and a newer pending run replaces an older one regardless of `cancel-in-progress`. The cleanup and deploy workflows shared the `gh-pages` group, so a cleanup queued behind a running deploy was dropped as soon as another deploy arrived. This is what happened on the release merge of #388: the `main` deploy held the group, the cleanup went pending, and the `stable/0.3` deploy then displaced it. The cleanup was cancelled before starting any job and `pr/388` stayed on `gh-pages`. Key the cleanup group on the pull request number, so each closure runs exactly once, and the deploy group on the ref, so deploys of different refs no longer displace each other. Writes to the branch were never relying on the group for correctness: the push-retry loop replays onto the updated tip. (cherry picked from commit 113213c12) Co-authored-by: Max Rossmannek <21973473+mrossinek@users.noreply.github.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
13951 of 14205 relevant lines covered (98.21%)
460128.92 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 39751541270.1 | 124 |
98.21
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|