the.com/rebase
git's way of rewriting your messy commit history like it went perfectly the first time.
means replaying your branch's commits on top of a different base commit, so history looks linear instead of tangled.
from from git's internal command git-rebase, introduced early on to let developers integrate changes without merge commits cluttering the log.
vs mergemerge preserves history, rebase pretends it was tidy
golden rulenever rebase commits others have already pulled
interactive modelets you squash, edit, or reorder commits freely
conflict costcan force you to resolve the same conflict twice