4 ms·
I would disagree with the strongly recommend here, because rebasing makes it so much easier to track down bugs and isolate breaking changes. Of course, this do
by joatmon-snoo 10y ago
I would disagree with the strongly recommend here, because rebasing makes it so much easier to track down bugs and isolate breaking changes.
Of course, this does require someone to be more proficient with Git beyond the simple add, commit, fetch, push model, which has its own drawbacks.
Also, at least in Git, squash is just one use case of interactive rebase, so I'm not quite sure what you're arguing against...
- hitsurume 10y agoCan you go more in depth with this process on how rebasing things makes it easier to track down bugs / breaking changes? Usually you can track down which feature branch is the one that cause a regression in your code base, and you can also look at specific commits to find out where problems happen. I can't tell how a rebasing flow would make this any easier?