Tie-in Squash Workflow with Branches #84
Description
Might be nice if you could tie the two together at some point into a broader workflow process.
i.e. we are told
"squash workflow," the one preferred by jj's creator, Martin
Ok, fine.
But then in 4.1 we have:
What anonymous branches are, and how to use them
But the "how to use them" doesn't (yet ?) cover "squash workflow" context.
It also doesn't cover "when" to use them, but maybe that's more of a personal preference thing, although some ideas/examples could be nice.
Maybe you need a part (9) ... "a day in the life of a dev using jj" which summarises everything into a nice workflow example based on jj "best practices".