After almost 8 years of professional career, I've used "git rebase" only once and quite recently to be honest 🙊🙊

I've found that without a ton of people working at once and just being methodical / careful about things .... haven't had to do a lot with git that wasn't super simple.

Maybe that's what's awesome about Git.

Still... I should know more.

@N00bPancakes I've always opted for the "merge" and "squash" strategy and I don't know how but every project I worked for used this. During my career, I worked on Mercurial and event Bazaar (BZR) but never tried rebase until now 😃

I pull rebase most of the times

I have yet to rebase.
I’ve never needed it 🤷🏻‍♀️

I bisect way more often than I rebase.

I've rebased repeatedly this month alone, mainly my branch on top of master, but also my changes on top of my other changes

In my project rebase with squash is the default merge option for the main repo. It looks much better when there's a desctiptive commit instead of yet another "merge <insert random branch name> into master". Also makes the whole tree much cleaner without all those dangling branches.

I only use rebase to squash my hundred commits like "typo", "fix small bug" into one before pushing

Same here :D Don’t even remember why.. Very difficult tool

@ctrl-alt-del why don't you amend small fixes fo the previous commit? 🤔

@iiii I do that too