Add PR rebase-and-retry workflow to unblock merge pipeline with 20 stalled PRs #160

New issue

Closed

opened 2026-04-08 23:01:50 -04:00 by pook · 5 comments

pook commented

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

Owner

ComplianceBot has 20 open PRs and ZERO recent merges — the entire merge pipeline is stalled. A CI workflow to auto-rebase PRs against main would unblock delivery.

Implementation:

Create .github/workflows/auto-rebase.yml triggered on push to main.
The workflow lists open PRs with passing CI checks and attempts git rebase origin/main for each.
If rebase succeeds, force-push the rebased branch.
If conflicts exist, add a 'needs-rebase' label and post a comment listing conflicting files.
Process max 3 PRs per run.

Acceptance criteria:

Workflow triggers on main push.
Clean rebases are pushed; conflicting PRs are labeled.
At least some PRs become mergeable after workflow runs.

Generated by CEO Planner (priority: 2)

ComplianceBot has 20 open PRs and ZERO recent merges — the entire merge pipeline is stalled. A CI workflow to auto-rebase PRs against main would unblock delivery. Implementation: 1. Create `.github/workflows/auto-rebase.yml` triggered on push to main. 2. The workflow lists open PRs with passing CI checks and attempts `git rebase origin/main` for each. 3. If rebase succeeds, force-push the rebased branch. 4. If conflicts exist, add a 'needs-rebase' label and post a comment listing conflicting files. 5. Process max 3 PRs per run. Acceptance criteria: - Workflow triggers on main push. - Clean rebases are pushed; conflicting PRs are labeled. - At least some PRs become mergeable after workflow runs. --- *Generated by CEO Planner (priority: 2)*

pook added the

agent-task

label

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

agent-bot referenced this issue from a commit

2026-04-08 23:04:41 -04:00

feat: issue #160 compliancebot-has-20-open-prs-and-zero-r (agent task agent-ta)

pook commented

2026-04-09 05:10:52 -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:33:48 -04:00

Author

Owner

⚠️ Stale Task Alert — This task has been open for 7h 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 7h 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 7h with no associated PR.

Possible causes: