User prefers deletion over archive for superseded repos (same-day migration)

User prefers deletion over archive for superseded repos

User prefers deletion over archive for superseded repos

The rule

When a repo is superseded by another (renamed, replaced, or rolled into a different repo) within the same day or active migration session, delete the superseded repo rather than archive it.

Same-day exception to never-delete-empty-placeholder-repos

The family rule never-delete-empty-placeholder-repos.md treats empty repos as deliberate slug reservations and requires explicit per-repo authorization for gh repo delete. This rule adds an exception: empty or stub-only repos that were superseded the same day they were created (or during an active migration session) can be deleted without the standard cooling-off, when the user confirms via MCQ.

When NOT to delete

• Repo has external clones / forks / stars beyond the user themselves.
• Repo has been live for >24 hours.
• Repo has any commits / issues from non-owners.
• Repo is referenced from external blog posts / résumé / npm repository field of a published package.

In those cases: archive (gh repo archive), don’t delete.

How to apply

When the user requests “delete unneeded repos after migration”:

1. List the candidates as a multi-select MCQ.
2. For each, check: created same day? Empty or stub-only? No external refs? If all yes — delete is safe.
3. Run gh repo delete <slug> --yes per confirmed candidate.
4. Update .gitmodules and submodule paths in the umbrella repo.
5. Commit + push the umbrella with a clear message naming what was deleted.

Source

Rule derived from explicit user preference per ~/AGENTS.md AskUserQuestion learning rule.

Edit on GitHub · Back to index