Repository hygiene, written down
Practical, evergreen guides on naming, archiving and backing up Git repositories. No fluff, no vendor pitch — the steps we run for clients.
Git Repository Naming Conventions: A Practical Guide for Teams
Every team ends up with api-v2, api_final, and API-NEW. A naming convention is how you stop that from happening again — here is one you can adopt in an afternoon.
how to archive a github repositoryHow to Archive a GitHub Repository (and When You Should Not)
Archiving is the right answer for most dead repositories — but it is not deletion, and it is not a backup. Here is exactly what changes, step by step.
how to save a github repository locallyHow to Save a GitHub Repository Locally: A Backup Guide That Actually Restores
A zip of the default branch is not a backup of your repository. Here are the three ways to save a repo locally, what each one keeps, and how to prove the copy works.
Want us to run this for you?
Send a note with how many repositories your team has and what worries you most. You will get a straight answer on whether a cleanup is worth doing.