Git workflows, tooling and the occasional strong opinion, from the team building Gitoryx. New posts every week.
6 posts in Guide
A bug report arrives and the first real question is when it started. Bisect answers that eventually. Reading the graph answers it faster, and often tells you the cause outright.
Read Article
Git has an answer for nearly every mistake. The hard part is knowing which command to reach for while your heart rate is elevated. Here is the triage, organised by what went wrong.
Read Article
Git almost never deletes a commit when you think it does. The reflog records everywhere HEAD has been, which means most of the moments that feel unrecoverable take about thirty seconds to fix.
Read Article
You know it worked two weeks ago and it is broken now, with two hundred commits in between. Bisect finds the culprit in eight steps instead of two hundred. Here is how to run it, automate it, and avoid the traps.
Read Article
One emoji at the front of a commit message tells you the type of change before you have read a single word. Here is the vocabulary worth learning, the tooling that makes it stick, and the mistakes that turn it into noise.
Read Article
Interactive rebase is the fastest way to turn a messy branch into something a reviewer can actually read. Here is what each command does, how to recover when it goes wrong, and why the todo file is the worst part of it.
Read Article