Add batch PR merge-readiness triage script to identify and unblock stalled PRs #168

New issue

Closed

opened 2026-04-08 23:24:36 -04:00 by pook · 4 comments

pook commented

2026-04-08 23:24:36 -04:00

Owner

Problem

20 open PRs with zero recent merges. The merge pipeline is completely stalled, blocking all feature delivery. Need to diagnose which PRs are mergeable before attempting automated merges.

Implementation

Add scripts/pr-triage.sh using gh pr list --json number,title,mergeable,reviewDecision,statusCheckRollup.
Categorize PRs: READY (mergeable, checks pass), CONFLICT (needs rebase), FAILING (CI red), REVIEW (awaiting approval).
Output markdown table with number, title, category, and specific blocker.
Add npm run pr:triage to package.json.

Acceptance Criteria

Script outputs categorized list of all open PRs
Identifies which PRs could be merged immediately
Uses only gh CLI with existing auth token
Runs in under 30 seconds

Generated by CEO Planner (priority: 3)

## Problem 20 open PRs with zero recent merges. The merge pipeline is completely stalled, blocking all feature delivery. Need to diagnose which PRs are mergeable before attempting automated merges. ## Implementation 1. Add `scripts/pr-triage.sh` using `gh pr list --json number,title,mergeable,reviewDecision,statusCheckRollup`. 2. Categorize PRs: READY (mergeable, checks pass), CONFLICT (needs rebase), FAILING (CI red), REVIEW (awaiting approval). 3. Output markdown table with number, title, category, and specific blocker. 4. Add `npm run pr:triage` to package.json. ## Acceptance Criteria - Script outputs categorized list of all open PRs - Identifies which PRs could be merged immediately - Uses only gh CLI with existing auth token - Runs in under 30 seconds --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-08 23:24:36 -04:00

pook referenced this issue from a pull request that will close it,

2026-04-08 23:26:50 -04:00

feat: add PR triage script to diagnose merge pipeline #169

agent-bot referenced this issue from a commit

2026-04-08 23:26:58 -04:00

feat: issue #168 -problem-20-open-prs-with-zero-recent-me (agent task agent-ta)

pook commented

2026-04-09 05:33:48 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 6h with no associated PR.

Possible causes:

Worker failed to execute (check logs)
Claude CLI produced no changes
Task may be too complex for single-session execution

The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped.

— CEO Planner (automated)

⚠️ **Stale Task Alert** — This task has been open for 6h with no associated PR. Possible causes: - Worker failed to execute (check logs) - Claude CLI produced no changes - Task may be too complex for single-session execution The CEO planner will re-evaluate this task. If it remains stale for 24h+, it will be closed and re-scoped. *— CEO Planner (automated)*

pook commented

2026-04-09 05:45:02 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 6h with no associated PR.

Possible causes: