Reconcile ambiguous merge outcomes after upstream timeouts #278

Merged
timmy merged 1 commits from timmy/277-reconcile-merge-timeouts into main 2026-08-08 07:34:43 +00:00
Owner

Closes #277

What changed

  • reconcile failed or timed-out merge responses against authoritative Gitea pull state and expected head SHA
  • return confirmed success for an accepted merge, or a truthful confirmation_pending response when state cannot be proven
  • preserve the pending-confirmation guidance in the mobile pull sheet

Tests

  • RED observed for accepted-before-timeout reconciliation
  • RED observed for authoritative merge-state lookup
  • RED observed for unresolved confirmation response
  • RED observed for mobile pending guidance
  • pytest -q — 489 passed
Closes #277 ## What changed - reconcile failed or timed-out merge responses against authoritative Gitea pull state and expected head SHA - return confirmed success for an accepted merge, or a truthful `confirmation_pending` response when state cannot be proven - preserve the pending-confirmation guidance in the mobile pull sheet ## Tests - RED observed for accepted-before-timeout reconciliation - RED observed for authoritative merge-state lookup - RED observed for unresolved confirmation response - RED observed for mobile pending guidance - `pytest -q` — 489 passed
timmy added 1 commit 2026-08-08 07:33:56 +00:00
fix: reconcile ambiguous merge outcomes (#277)
All checks were successful
CI / lint (pull_request) Successful in 26s
CI / build-frontend (pull_request) Successful in 5s
e58808f2d4
timmy merged commit b11ec6a732 into main 2026-08-08 07:34:43 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#278
No description provided.