Add auto-merge script for CI-passing PRs to clear merge backlog #122

Closed
opened 2026-04-08 20:34:38 -04:00 by pook · 1 comment
Owner

ComplianceBot has 20 open PRs and 0 merged — the pipeline is completely blocked at the merge stage. Once CI is gating PRs, an auto-merge mechanism is critical to clear the backlog.

Create scripts/auto-merge.sh:

  1. Query Forgejo/GitHub API for all open PRs
  2. For each PR: check CI status (all checks pass), check for merge conflicts
  3. Squash-merge qualifying PRs in priority order (oldest first)
  4. Post merge comment with summary
  5. Support --dry-run flag for safe preview

Acceptance criteria:

  • Only merges PRs where all CI checks pass and no conflicts exist
  • Squash merge with PR title as commit message
  • Dry-run mode shows what would be merged
  • Handles API rate limits gracefully
  • Logs merged PR numbers and skipped PR numbers with skip reason

Generated by CEO Planner (priority: 2)

ComplianceBot has 20 open PRs and 0 merged — the pipeline is completely blocked at the merge stage. Once CI is gating PRs, an auto-merge mechanism is critical to clear the backlog. Create scripts/auto-merge.sh: 1. Query Forgejo/GitHub API for all open PRs 2. For each PR: check CI status (all checks pass), check for merge conflicts 3. Squash-merge qualifying PRs in priority order (oldest first) 4. Post merge comment with summary 5. Support --dry-run flag for safe preview Acceptance criteria: - Only merges PRs where all CI checks pass and no conflicts exist - Squash merge with PR title as commit message - Dry-run mode shows what would be merged - Handles API rate limits gracefully - Logs merged PR numbers and skipped PR numbers with skip reason --- *Generated by CEO Planner (priority: 2)*
Author
Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

  1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
  2. CEO should halt new task creation until open PRs drop below 10
  3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.
pook closed this issue 2026-04-10 14:48:28 -04:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
pook/compliancebot#122
No description provided.