Gio Lodi • 3/9/2022

The case for creating a merge commit

This article advocates for using GitHub's 'Create a merge commit' merge strategy over 'Squash and merge' or 'Rebase and merge'. It explains how this approach preserves a detailed history of small, atomic commits on the main branch while still allowing for a high-level view via `git log --first-parent`. The author argues this optimizes for understanding code evolution, aids in bisecting and reverting, and keeps all project history directly in Git.

0 comments

#software development #github #git