Or why a clean commit history can help quite a lot to find how and why a bug was introduced. This shows a few nice tricks around git log to speed up the process.

Good explanations on how HEAD works in git and what it means. It's indeed one of those terms where the consistency isn't great in git.

Looks like an interesting approach for a new family of development forges. Fully distributed and peer to peer, I wonder if it'll pick up.

Good reminder that git worktrees exist. They definitely come in handy sometimes.

Going back on the history of the introduction of version control in software engineering and how Git ended up so dominant. We often forget there was a time before Git.

Nice list of tips and recent git features to manage large repositories.

Indeed the example is a bit extreme. Still it illustrate quite well what should be found in a commit message. It needs to tell a story and motivate the reasons behind a change.

A nice knowledge base about what is probably my favorite branching model. Goes in the variations you can have, the trade-offs and the other techniques you need to bring in for it to work well.

So, which team are you on when you think about commits in Git?

It looks like git workflows using rebase are becoming the norm. People are actively trying to avoid merge commits in their repository history. Tooling support could be a bit better though.

Back to the history of VCS, anyone still remember and used SCCS? Well, I did use it...

Interesting statistics, this show how important it is to have well structured and focused change sets as much as possible.

A good reference on most of the branching patterns you can find. From this you can derive your project wide policy. Also it's spot on when it says that branching is easy but each time you branch you need to keep in mind how you're going to merge.