Repository navigation
fix: converge concurrent issue completion safely - #629
Conversation
|
To preview the documentation for this pull request, visit the following URL:
|
Bugbot: review complete
|
Copilot approval · Human review neededStatus: A protected workflow, policy, or trust-boundary file changed. Technical evidenceRevision: |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #629 +/- ##
===========================================
+ Coverage 90.94% 94.10% +3.16%
===========================================
Files 135 950 +815
Lines 6251 30548 +24297
Branches 1338 8965 +7627
===========================================
+ Hits 5685 28748 +23063
- Misses 172 704 +532
- Partials 394 1096 +702
🚀 New features to boost your workflow:
|
|
/copilot sync-branch |
…low-stale-after-successful-pr-completion
Branch synchronized
The fixer resolved 8 conflicted files. 6 verification checks passed. |
Concurrent merged-PR and closed-issue workflows now converge after freshly verifying native closure, metadata and exact owned-card retirement. A verified duplicate is explicit in the Job Summary; reopened/reason-changed issues and incomplete cleanup still fail with bounded causal recovery details.
What changed
Validation
No global suppression of workflow.stale is introduced. A promoted consumer completion sequence is still needed for live acceptance; the original incident did not establish its exact failing fence.
Closes #622