Guard progress state against stale branch heads - #384
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #384 +/- ##
===========================================
+ Coverage 90.94% 92.84% +1.89%
===========================================
Files 135 654 +519
Lines 6251 17217 +10966
Branches 1338 4410 +3072
===========================================
+ Hits 5685 15985 +10300
- Misses 172 484 +312
- Partials 394 748 +354
🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Current status: Overall coverage is partial; this snapshot does not prove that all of its findings are resolved.
Last reconciled on1ef7ec4. See aggregate Bugbot status.
🤖 Bugbot review snapshot
Bugbot reported 1 potential problem when commit f488daa was analyzed. This snapshot is historical; use the status block above for current state. 1 finding is linked to changed code.
Findings
- medium: Do not use the workflow SHA as the selected progress branch head —
src/actions/github_event_inputs.ts:37
Bugbot: review incomplete
Incomplete coverage
|
f488daa to
f2adb6b
Compare
…t stale branch heads
f2adb6b to
1ef7ec4
Compare
Publication now verifies that generated results still match the authoritative branch head before mutating GitHub. This prevents stale progress and status updates from overwriting newer source state and records skipped work as structured stale-source evidence.
What changed
Review notes