I’ve found megamerge really helpful in cases where I’m working on a change that touches multiple subsystems. As an example, imagine a feature where a backend change supports a web change and a mobile change. I want all three changes in place locally for testing and development, but if I put them in the same PR, it becomes too hard to review—maybe mobile people don’t want to vouch for the web changes.
You’re right that I have to make sure that the backend changes don’t depend on the mobile changes, but I might have to be mindful of this anyway if the backend needs to stay compatible with old mobile app versions. Megamerge doesn’t seem to make it any harder.
Depends what you mean by “synced”—do you want your beads state to be coupled with commits (eg: checking out an old commit also shows you the beads state at that snapshot)? Using a separate branch would decouple this. I think the coupling is a nice feature, but it isn’t a feature that other bug trackers have, so using a separate branch would make beads more like other bugtrackers. If you see the coupling as noise, though, then it sounds like that is what you want.
For what it's worth (maybe not much from an internet stranger), I couldn't possibly overstate how much I love my Ridgeline. I love the trunk under the bed, I love how the back seats fold up for extra in-cab cargo space, and I love how the unibody structure and independent rear suspension make it drive like a car. It's comfortable enough that I can use it happily for longer road trips.
I love it so much that when it was stolen on a trip to Montreal a few years ago, I bought the exact same year and model again without even googling other options.
It is a bit longer than I'd prefer--I live in urban Chicago and occasionally do have to forgo a good parking space, but usually those are, like, Honda Civic spaces that a slightly smaller truck wouldn't fit into either.
You’re right that I have to make sure that the backend changes don’t depend on the mobile changes, but I might have to be mindful of this anyway if the backend needs to stay compatible with old mobile app versions. Megamerge doesn’t seem to make it any harder.