Skip to content
loading...
markdown guide
 

The simple explanation is that each commit in git has one or more 'parents', which are commits that come logically before it in the change history, and git rebase changes what the parent of the base commit (that is, the commit that you started the branch from) in a branch is. Essentially, if you think of each commit as a folder in the filesystem, it's parent is the folder that contains it, and git rebase is equivalent to moving it into a different folder (of course, with lots of extra stuff to sanely handle conflicts).

This is useful for a number of things:

  • Assuming you have a branch B based on another branch A, it lets you update B to include changes from A without needing a merge commit. This usually results in history that much is easier to understand than if you had merged A into B to do the same update. The general syntax for this is git rebase A B (or, if you have branch B checked out, git rebase A). In many workflows, this is the preferred way of updating branches that you have not published anywhere because it helps keep the history simple. This is about 95% of what most people will ever need git rebase for.
  • Assuming you have a branch C based on a branch B but need it to be based on a different branch A, it lets you transplant branch C so that it's based on branch A instead of branch B. This is useful when you accidentally start a branch from the wrong base. The general syntax for this is git rebase --onto A B C. This covers a significant majority of the remaining 5% of what most people will ever need it for.
  • Because git rebase can take tags or even commits instead of branch names, you can use it to move individual commits or sequences of consecutive commits from one branch to another with the git rebase --onto syntax. This is useful when you end up developing a fix for an existing bug as part of developing a new feature, and need to submit that fix separately from the new feature. Note however that git cherry-pick plus a carefully crafted git reset is often preferred here, as it's a lot easier to get right than doing the same thing with git rebase --onto (and it's usually easier to fix if you get it wrong).
  • Similarly because of the fact that it accepts commits or tags, you can use git rebase to remove a series of commits from further back in the history of a branch using the git rebase --onto syntax. This is not something that is frequently needed if you're doing your development work properly, but if you haven't published a branch yet, this may be preferable to reverting a prior commit in the branch as it will make the history more concise.
  • Aside from the above, you can perform arbitrary transformations to the history of a branch by doing an interactive rebase (git rebase -i, also works with the the --onto syntax, though that tends to be very confusing so it's generally not the best idea to do it in one step (you can always git rebase -i and then git rebase --onto as two separate steps)). This is only very rarely needed in a vast majority of development workflows (especially if you're doing your development work right), but it lets you do very complex things like splitting a commit into multiple commits, merging a bunch of commits into one, reordering the commits on the branch, or even just running a given command in the working tree for each commit on the branch (useful for testing proper bisectability of a sequence of changes, which is a major reason that git rebase -i exists in the first place).

There is, however, one very big caveat to using git rebase. Because it modifies history, you have to use a force push whenever you rebase a branch and then have to update a remote copy of that branch. This plus the rewritten history makes it very difficult for others to update copies of that branch in any clones of the repository (it requires them to delete their local copy of the branch, re-fetch the refs for it from the remote, and then check it out again), especially if they have any local work based on it. As a result, the general advice is to avoid rebasing any published branches outside of situations that you've agreed with your coworkers that it's acceptable to do so.

You may also want to look at git cherry-pick, which lets you copy commits from one place to another (unlike git rebase, which functionally moves commits).

 
 
 

Take your three favorite books and put them on top of the evergrowing pile of books to read so that even though you keep buying books your three favorite books will be fresh at the top of the pile

:-D

 

Rebase is another way to integrate changes from one branch to another. Rebase compresses all the changes into a single “patch.” Then it integrates the patch onto the target branch. Unlike merging, rebasing flattens the history because it transfers the completed work from one branch to another.

 

Rebase does no perform any flattening, unless you tell it to.

 

Hi, nice question!

Git commands such as merge and rebase allow you to integrate modifications in your branch.

Git merges take all histories into account without changing anything in your branch that's why it's called a non-destructive operation. Git rebases might be riskier.

But why/when rebasing? Merging all the time may pollute your history with a lot of unnecessary merge commits. You want linear histories that's why pull by rebasing is better than pull by merging IMHO (default is merge):

git config --global pull.rebase true

You won't have a history full of messages like "merge master into master". You can verify this assertion with the git log command.

Pull by rebasing is super extra cool. If someone pushes modifications before you and you have made some commits locally in the meantime, you just have to pull and Git will automatically apply your commits after. So history remains nice and clean.

BUT manual rebasing is quite risky. So be extra cautious with this command. You might destroy Gotham :)
For example, if you run a manual rebase of master in your branch:

git rebase master

you cannot push just after. You need to run a push --force to override the remote master branch to match the rebased one from your local. You might run this only in very particular cases. Otherwise, you could mess up things for you and your teammates.

source

 

A JavaScript visualization:

Git.rebase == YouTube.watch_later // true
Git.rebase === YouTube.watch_later // false
 

Well, did you ever play towers of hanoi when you were 5?

You're tasked with rebaseing your commits to a different peg. The difference is, you can take any number and apply them in any order to any peg.

Classic DEV Post from Jun 5 '19

Are we "developers" gatekeeping "knowledge" from our juniors and peers? 🤦

The subconscious role we "senior developers" play, in preventing the spread of knowledge without us realizing. And stifling the growth of all around us.

David Mendoza 🇭🇳 profile image
I'm a Honduran developer who loves to program all that he can and if I can't I would try anyway.

Need dark mode?

Create your account (free forever) to customize your experience.

Get Started