feat(bonedigger): add clanker-queue migration workflow - #33
Conversation
- add a canonical labels.json with the new clanker-queue/* namespace - add sync-labels.yml to propagate labels.json to the factory repos - dual-write legacy labels and clanker-queue labels in the reusable lifecycle workflow during the soak - update the repo docs and skills to describe the new ownership model Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
hanthor
left a comment
hanthor
left a comment
There was a problem hiding this comment.
Two rollout invariants need fixing. First, labels.json defines clanker-queue/p0 and p1 as replacements for cycle-wide hive priorities, while lifecycle.yml applies them at the repo-scoped priority/p0 and priority/p1 confirmation thresholds. That collapses two distinct severities without a consistent mapping. Second, the legacy and clanker labels are added in one gh issue edit guarded by a single or-true; before sync-labels has created the new labels downstream, the missing clanker label can make the whole edit fail and suppress the legacy update too. Please define one consistent priority mapping and make dual writes independent or otherwise guarantee the new labels exist before any pinned caller can execute. The workflow PR also needs the required actionlint and pre-commit verification evidence.
2 participants
Adds the clanker-queue migration namespace to bonedigger:
This is the rollout branch that the downstream bonedigger callers pin to.