Remix.run Logo
▲ zahrevsky 32 minutes ago

What I miss is a guide on how a good commit history should look like, ideally focused on real-world examples.

There's lot's of jujutsu tutorials that teach you how to undo operations and write commit messages before the commit, but almost none cover what to do with all this power.

It's easy to name some general principles like “it should be easy to read” but I don't think it helps, especially if you're a novice like me.

▲jgtrosh 23 minutes ago | parent | next [-]

Jujutsu tries to be nonprescriptibe about the end result, but my understanding of the megamerge strategy is that you want the powerful rebasing to help you manipulate many branches in parallel (fixes, features, etc), test them together, and end up with a linear history once accepted each is accepted. This isn't a real world example though.

▲hdjrudni 21 minutes ago | parent | prev [-]

Google offers some advice on how to write good commit messages: https://google.github.io/eng-practices/review/developer/cl-d...