[{"data":1,"prerenderedAt":14},["ShallowReactive",2],{"post-git-habits-for-small-teams":3},{"_path":4,"title":5,"description":6,"date":7,"tags":8,"readingTime":12,"body":13},"\u002Fblog\u002Fgit-habits-for-small-teams\u002F","Git Habits for Solo and Small Teams","Branch naming, commit messages, and PR hygiene that keep history useful without slowing you down.","2026-01-09",[9,10,11],"git","workflow","productivity",1,"# Git Habits for Solo and Small Teams\n\nYou do not need a heavyweight process to keep git history readable. A few consistent habits go a long way—even on a solo portfolio repo.\n\n## One idea per commit\n\nCommits should answer “why did this change land?” Prefer a short subject that states intent:\n\n```text\nAdd blog post index for static prerender routes\n\nFix mobile nav focus order after menu close\n```\n\nAvoid dumping unrelated formatting and feature work in the same commit when you can split them cleanly.\n\n## Branches that explain themselves\n\nUse names that hint at the work: `blog\u002Fmore-posts`, `fix\u002Fnav-focus`, `chore\u002Fupdate-deps`. Delete merged branches so the list stays short.\n\n## Protect main, ship in small steps\n\nWhether you push straight to `main` or open PRs for yourself, keep changes reviewable. Smaller diffs are easier to revert and easier to bisect when something regresses after deploy.\n\n## Wrap-up\n\nGood git hygiene is about future you: clear commits, short-lived branches, and a main branch you trust to deploy.",1784110285919]