[Fleet Monitor] petry-projects/.github-private — dev-lead.yml #341

Activity

1. don-petry

   added

   health-checkAutomated health check reportAutomated health check report

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   fleet-trackerTracked by the Actions Fleet MonitorTracked by the Actions Fleet Monitor

   on May 21, 2026
2. don-petry

   added

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   and removed

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   on Jun 8, 2026
3. don-petry commented on Jun 9, 2026

   

   don-petry

   on Jun 9, 2026

   CollaboratorAuthor

   More actions

   All engines are currently rate-limited. Please re-apply the `dev-lead` label when the rate limit clears to retry.
4. don-petry

   added

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   and removed

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   on Jun 9, 2026
5. don-petry commented on Jun 9, 2026

   

   don-petry

   on Jun 9, 2026

   CollaboratorAuthor

   More actions

   Dev-Lead Implementation Plan

   Issue: #341 — [Fleet Monitor] petry-projects/.github-private — dev-lead.yml

   Scope

   Fix the two runtime failure modes causing the 14.5% failure rate in dev-lead.yml: (1) checkout_pr_in_worktree crashing when a PR is merged and its branch deleted before checkout, and (2) push_with_merge_guard failing the workflow when a push is rejected due to concurrent runs.

   Root Cause Analysis

   From workflow run logs, two distinct runtime failures are responsible for the failure rate:

   1. Closed/merged PR checkout failure (scripts/lib/pr-worktree.sh)

   • Error: fatal: couldn't find remote ref refs/heads/<branch>
   • Seen in runs for PRs fix(dev-lead): release stale PR-branch worktrees before checkout (#470) #494, feat(initiative): dependency-aware driver to deliver epics agentically #507, and others
   • When a PR is merged and its branch deleted, but a dev-lead event (e.g., a bot review comment) was already queued, checkout_pr_in_worktree calls gh pr checkout which fails trying to fetch the deleted branch
   • hold_auto_merge only guards the race when auto-merge is enabled; when auto-merge is already OFF, it returns early without checking if the PR is open

   2. Concurrent push rejection (scripts/lib/auto-merge.sh)

   • Error: Updates were rejected because the remote contains work that you do not have locally.
   • Seen in run 27181648446 on PR feat: implement issue #408 — petry-projects — workflow failures detected 2026-05-29 #477 (and others)
   • When two dev-lead runs both commit to the same branch, the second push is rejected with "fetch first"; push_with_merge_guard treats this as a hard failure (returns 1) when PR is still open

   Implementation Checklist

   • scripts/lib/pr-worktree.sh: in checkout_pr_in_worktree, catch gh pr checkout failures and check PR state — exit 0 cleanly if PR is closed/merged
   • scripts/lib/auto-merge.sh: in push_with_merge_guard, detect "fetch first" rejection and attempt git pull --rebase + retry; if retry fails, exit 0 (concurrent run handled it)

   Tests to Write

   • tests/dev-lead/unit/test_pr_worktree.bats: new test — checkout exits 0 when gh pr checkout fails and PR is closed/merged
   • tests/dev-lead/unit/test_auto_merge.bats: new test — push_with_merge_guard retries with pull-rebase on fetch-first rejection and succeeds
   • tests/dev-lead/unit/test_auto_merge.bats: new test — push_with_merge_guard exits 0 cleanly when rebase/retry also fails (concurrent run scenario)

   Test Command

   bash scripts/dev-lead-lint.sh
   (Full bats tests require sudo apt-get install bats which isn't available locally; the CI bats suite at .github/workflows/ci.yml covers the unit tests.)
6. don-petry commented on Jul 15, 2026

   

   don-petry

   on Jul 15, 2026

   CollaboratorAuthor

   More actions

   ✅ Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-06-04 (41 days) — the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.
7. don-petry

   closed this as completedon Jul 15, 2026