okhp3-repository-janitor

Topics in the source

• okhp3-repository-janitor
• Safety contract
• Audit workflow
• Scheduled operation
• Output contract
• Resources
• About

OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Keep a multi-repository Git estate understandable without losing work. Treat origin/main as the comparison baseline, not as evidence that other work is disposable. 1. Begin with a read-only inventory. Do not delete repositories, branches, stashes, refs, or commits during discovery. 2. Preserve before pruning. Record dirty files, stashes, local-only commits, and unreachable commits. Pin unreachable commits under a dated refs/archive/ namespace before a later cleanup can trigger garbage collection. 3. Refresh remotes with git fetch origin; do not use --prune until stale remote branches have been classified. 4. Compare each checkout to the refreshed origin/main. Report both file-level and commit-level differences. 5. Treat a merged branch, a closed pull request, and an abandoned branch as different facts. Query the pull request before deletion. 6. Merge only a reviewed pull request whose checks and destination are suitable. Do not merge a branch merely because it is old or has a bot name. 7. Delete a remote branch only when its merged/superseded status, commit reachability, and pull-request state are confirmed. Delete the local tr

This is an excerpt. Refer to the complete source and its current requirements.