Add PR auto-labeling job to CI workflow for merge triage #121

New issue

Closed

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

pook commented

2026-04-08 20:34:38 -04:00

Owner

ComplianceBot has 20 open PRs and zero merged PRs — this is a critical pipeline bottleneck. The CI quality gate (PR #92) needs to be supplemented with auto-labeling so mergeable PRs are visible.

Add to the CI workflow:

A job that runs after test/typecheck/lint jobs complete
On all-pass: add 'ready-to-merge' label via Forgejo/GitHub API
On failure: add 'needs-fix' label, remove 'ready-to-merge', post comment with failure details
Ensure the workflow handles the case where CI gate PR #92 hasn't merged yet (graceful skip)

Acceptance criteria:

Passing PRs get labeled 'ready-to-merge'
Failing PRs get labeled 'needs-fix' with actionable comment
Labels update on subsequent pushes
No PRs sit unlabeled after CI completes

Generated by CEO Planner (priority: 3)

ComplianceBot has 20 open PRs and zero merged PRs — this is a critical pipeline bottleneck. The CI quality gate (PR #92) needs to be supplemented with auto-labeling so mergeable PRs are visible. Add to the CI workflow: 1. A job that runs after test/typecheck/lint jobs complete 2. On all-pass: add 'ready-to-merge' label via Forgejo/GitHub API 3. On failure: add 'needs-fix' label, remove 'ready-to-merge', post comment with failure details 4. Ensure the workflow handles the case where CI gate PR #92 hasn't merged yet (graceful skip) Acceptance criteria: - Passing PRs get labeled 'ready-to-merge' - Failing PRs get labeled 'needs-fix' with actionable comment - Labels update on subsequent pushes - No PRs sit unlabeled after CI completes --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-08 20:34:38 -04:00

pook commented

2026-04-10 14:48:28 -04:00

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:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
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

No labels

agent-task

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#121

No description provided.

Rows
Columns