build:added some excplict priorities

2026-04-12 23:45:01 -04:00
parent d5446081e3
commit 96ff9d0ff8
3 changed files with 5 additions and 5 deletions
@@ -150,9 +150,9 @@ Poll every 2 minutes using `bash("sleep 120", timeout=180000)`.

 Each cycle:

-1. **Discover PR work.** List all open bot PRs. For each one without an active worker and not labeled `needs feedback`, determine the escalation tier from its comment history, and queue it for dispatch.
+1. **Discover PR work.** List all open bot PRs that have either a review requesting changes or CI quality gates that are failing. For each one without an active worker and not labeled `needs feedback`, determine the escalation tier from its comment history, and queue it for dispatch.  Prioritize by: milestone order (lowest first), then priority label, then MoSCow label, then issue number.

-2. **Discover issue work.** List open issues in `State/Verified` or `State/In Progress` with no active worker. Respect dependencies — don't dispatch an issue that depends on an unresolved blocker. Prioritize by: milestone order (lowest first), then priority label, then issue number. Determine escalation tier from comment history.
+2. **Discover issue work.** List open issues in `State/Verified` or `State/In Progress` with no active worker. Respect dependencies — don't dispatch an issue that depends on an unresolved blocker. Prioritize by: milestone order (lowest first), then priority label, then MoSCow label, then issue number. Determine escalation tier from comment history.

 3. **Dispatch workers.** Fill all available worker slots, PR work first. Specify the escalation tier for each worker. Track which issues/PRs have active workers to avoid duplicate dispatch.

@@ -122,7 +122,7 @@ Poll every 5 minutes using `bash("sleep 300", timeout=360000)`.

 Each cycle:
 1. List all open PRs.
-2. For each PR, check the listed merge criteria.
+2. For each PR, check the listed merge criteria.  Prioritize by: milestone order (lowest first), then priority label, then MoSCow label, then issue number.
 3. Merge (using fast-forward) any PR that passes all of the criteria (with mandatory post-merge verification).
 4. Dispatch rebase workers for PRs that are behind.
 5. Update linked issues to `State/Completed` after verified merges.
@@ -79,11 +79,11 @@ Poll every 3 minutes using `bash("sleep 180", timeout=240000)`.

 Each cycle:

-1. **Discover PRs needing review.** List all open PRs. A PR needs review if: it was created by the primary bot account, it has no approving review yet, and it doesn't have a `needs feedback` label.
+1. **Discover PRs needing review.** List all open PRs. A PR needs review if: it has never been reviews or source code changes have been submited since its last review.

 2. **Skip already-covered PRs.** Check for existing worker sessions by tag before dispatching.

-3. **Dispatch reviewers.** Fill available worker slots with PRs needing review. Prioritize older PRs (lower PR number first).
+3. **Dispatch reviewers.** Fill available worker slots with PRs needing review.  Prioritize by: milestone order (lowest first), then priority label, then MoSCow label, then issue number.

 4. **Monitor workers.** Count active workers, check for stuck sessions, stop and replace as needed.