kentcdodds Cleanup after migrations
Read
docs/contributing/cleanup-after-migrations.md.
Do not leave untracked cruft.
Decision
- Do it now when the leftover is safe to drop with this change.
- Open a GitHub issue when it must wait on a later migration, a second deploy, a soak or metrics gate, a fleet apply, or another cutover.
A runbook or TODO is not the tracker. The issue is.
Search open Cleanup: issues first. Title:
Cleanup: <what to remove> after <gate>. Label: improvement. Link the issue
from the introducing PR.
## Leftover
What to delete or stop serving.
## Why it waits
The gate.
## Ready when
A falsifiable criterion (not a calendar date alone).
## How to verify
Commands, queries, or deploy evidence.
## Introduced by
PR that added the leftover.
gh issue create --title "Cleanup: … after …" --label improvement --body-file -
Or kody:@kentcdodds/github/request POST /repos/kentcdodds/kody/issues.
Soak or calendar gates also get a scheduled wake (execute +
workflows.create({ runAt, idempotencyKey })) per
ship-pr. Close the issue when the cleanup lands.