You are legally required not to move until that boiiii wakes up.

Ain’t nobody got time for that.

R E I S U B

enhanced photosynthesis

git add . && git commit -am “Add required dependencies”

5 interdependent modules? how sweet…

Because rebasing changes the history, which would mess with other people’s copies of the same branch, wherefore it shouldn’t be default.

I use rebase only to clean up some commit messages, squash commits, etc. - essentially to clean up feature branches I wrote. But never rebase to ‘move’ my branch as if it originated from a different commit, because I don’t know necessarily know what changes have been introduced on the other branch (typically main/master), so rebasing on that would leave my commits in a state that they were never tested in, possibly broken / with unintended sideeffects. If I need changes from the other (main) branch in my feature branch (because of feature dependencies, or to fix merge conflicts), I merge it into my branch and can be sure that the commits created before that merge still behave the way they did before that merge - because they were not changed; this can’t be said for rebasing.