3 ms·
Sounds like you've moved the work forward, where it always has to be done. Rather than doing it in a lazy manner, where most instances can be avoided. Is that
by mixmastamyk 6y ago
Sounds like you've moved the work forward, where it always has to be done. Rather than doing it in a lazy manner, where most instances can be avoided. Is that a good trade-off?
- NateEag 6y agoLike most tradeoffs, it depends on the particular circumstances, I think. I don't have this set up in my current gig, because we have more pressing priorities. It is incredibly useful when you do have it, though. Generally it's more important for really large projects - IIRC Android is really strict about not merging branches containing any commits that break tests, for exactly this reason. As that implies, you wind up rewriting branches in this approach, too, but for different reasons.