The Git Commands I Run Before Reading Any Code
piechowski.io · 849 words · saved by 1 readers
Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns.
The Git Commands I Run Before Reading Any Code The first thing I usually do when I pick up a new codebase isn't opening the code. It's opening a terminal and running a handful of git commands. Before I look at a single file, the commit history gives me a diagnostic picture of the project: who built it, where the problems cluster, whether the team is shipping with confidence or tiptoeing around land mines. What Changes the Most git log --format = format: --name-only --since = "1 year ago" | sort | uniq -c | sort -nr | head -20 I run this from app/ or src/ , not the repo root. Lockfiles,
saved by
related reading
- How to Write a Git Commit Messagecbea.ms
- Cognitive load is what mattersminds.md
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- How Core Git Developers Configure Git | Butler's Logblog.gitbutler.com
- Useful git commands for SRE and DevOps engineersreliabilityengineering.substack.com
- Git from the Bottom Upjwiegley.github.io
- How to read a codeiamjonas.me
- A successful Git branching model >> nvie.comnvie.com
- A Note About Git Commit Messagestbaggery.com
- Using Gitcs61bl.org
- Git - user-manual Documentationgit-scm.com
- Oh Shit, Git!?!ohshitgit.com