I like Git commit messages. Used well, I think they’re one of the most powerful tools available to document a codebase over its lifetime. I’d like to illustrate that by showing you my favourite ever Git commit.
Well, there’s different workflows. Big organizations tend to meticulously craft these branches and then do a big bang merge at the end.
But for smaller organizations/teams, it’s usually more useful to merge as early as possible, i.e. work directly on a single branch together. This avoids complex merge conflicts and allows others to benefit from your work as early as possible.
In particular, smaller teams tend to also go together with smaller projects, where many features may be completed in a single commit, so there’s not much of a backstory to tell…
Well, there’s different workflows. Big organizations tend to meticulously craft these branches and then do a big bang merge at the end.
But for smaller organizations/teams, it’s usually more useful to merge as early as possible, i.e. work directly on a single branch together. This avoids complex merge conflicts and allows others to benefit from your work as early as possible.
In particular, smaller teams tend to also go together with smaller projects, where many features may be completed in a single commit, so there’s not much of a backstory to tell…