The history-destroying problems of rebasing are a rant on their own.
That's a UI problem with git making it hard to find hidden commits (pre-rebase). The commits aren't destroyed, they are hidden. The Jujutsu CLI is nice because it fixes this UI problem.
Rebase itself is also often used to work around UI issues of git log to present a "clean history".
Can you say more? I use rebase to avoid history destruction/obscuration. Do you mean squash? If so then I agree.
Eh, squash has its place, too. Sometimes I made a simple typo, so I make another commit that fixes the typo and I squash the last two commits.
That's a UI problem with git making it hard to find hidden commits (pre-rebase). The commits aren't destroyed, they are hidden. The Jujutsu CLI is nice because it fixes this UI problem.
Rebase itself is also often used to work around UI issues of git log to present a "clean history".
Can you say more? I use rebase to avoid history destruction/obscuration. Do you mean squash? If so then I agree.
Eh, squash has its place, too. Sometimes I made a simple typo, so I make another commit that fixes the typo and I squash the last two commits.