Get the latest tech news
Things I know about Git commits
Some of the things I've learned over a decade of Git usage, and working on writing good commit messages.
This is an article that's been swimming around in my head for ~5 weeks now, and may become a "living post" that I keep updated over time. This is a mix of experience in companies with teams of 2-12 people, as well as in Open Source codebases with a vast range of contributors. Then squash-merge, then merge If you don't learn how to rebase, you're missing out on a good skill People who say "just delete the repo" when things go wrong really frustrate me Learn how to use git reflog, and it'll save you deleting a repo and work that was recoverable Learn how to use git reflog, and you'll be able to save yourself from mistakes that aren't that bad No amount of learning fancy tools and commands saves you from fucking up every once in a while My most recent botched rebase was last week, and I needed git reflog to help un-fuck it Learn how to undo a force push and then how to more safely force push(remember the=ref!!)
Or read this on Hacker News