fix: Refinery queue uses beads MQ as source of truth (hq-eggh5)
The refinery was checking git branches instead of the beads merge queue. This caused MRs to pile up when branches were deleted but MR beads remained. - manager.go: Queue() now queries beads for type=merge-request issues - refinery.md.tmpl: Updated queue-scan to use gt mq list - mol-refinery-patrol.formula.toml: Updated queue-scan step instructions
This commit is contained in:
@@ -198,12 +198,12 @@ gt mail inbox
|
||||
# Process each message: lifecycle requests, escalations
|
||||
```
|
||||
|
||||
**queue-scan**: Fetch remote and identify branches
|
||||
**queue-scan**: Check beads merge queue (source of truth)
|
||||
```bash
|
||||
git fetch origin
|
||||
git branch -r | grep polecat
|
||||
gt refinery queue {{ .RigName }}
|
||||
git fetch --prune origin
|
||||
gt mq list {{ .RigName }}
|
||||
```
|
||||
The beads MQ is the source of truth for pending merges, not git branches.
|
||||
If queue empty, skip to context-check step.
|
||||
|
||||
**process-branch**: Pick next branch, rebase on main
|
||||
|
||||
Reference in New Issue
Block a user