No org migration without grill-me + queue
No org migration without grill-me + queue
Rule
Moving any repo between GitHub orgs / user accounts requires:
- Grill-me session first — walk the decision tree, resolve the 5 known friction modes (PR attribution,
maintainer_can_modify, URL redirect rot, GH Pages break, star history), and reach a locked answer. - Migration queue entry — write to
knowledge/decisions/agent-tooling/migration-queue.mdwith: date opened, source, target, rationale, blockers-resolved list. - 6-month freeze respect — if fewer than 180 days since last migration for this repo, block by default. Queue entry must justify override.
Why
4 org migrations in 8 days (2026-06-25 through 2026-07-03) forced this rule. Compound costs surfaced:
- GitHub Pages CNAME resets → live sites broke
- GH Actions references silently broken (no auto-redirect for security)
- Star history + fork graph attribution rot
- Old-org name reserved for only ~1 year, then reclaimable by squatters
- Inbound links, package registries, jsDelivr caches drift
Where the rule fires
- User asks "move X to Y org" or "should we recreate oriz-org"
- Any workflow that would call
gh api repos/<owner>/<repo>/transfer - Any batch that touches
.gitmodulesURL fields at scale
Anti-patterns
- ❌ Transferring a repo without a grill-me lock
- ❌ Skipping the queue write because "it's just one repo"
- ❌ Migrating within 180 days of last move without explicit queue override