{"id":101,"date":"2022-04-29T03:04:50","date_gmt":"2022-04-29T03:04:50","guid":{"rendered":"https:\/\/blogs.oregonstate.edu\/youhadmeatcode\/?p=101"},"modified":"2022-04-29T03:06:28","modified_gmt":"2022-04-29T03:06:28","slug":"git-ready-to-rebase","status":"publish","type":"post","link":"https:\/\/blogs.oregonstate.edu\/youhadmeatcode\/2022\/04\/29\/git-ready-to-rebase\/","title":{"rendered":"Git Ready to Rebase"},"content":{"rendered":"\n

The basics of git rebase.<\/h2>\n\n\n\n

Hello again! This week the team ran into some git trouble which led to me tumbling down a git rabbit hole. Seems fitting that it would be a R-abbit hole, since the primary commands I needed to sort through were R-eset, R-evert, R-estore, and R-ebase. Today though, we will be focusing primarily on git’s rebase command. Rebasing is exactly what it sounds like you are changing the commit that a particular branch or commit connects to. First, we will take a look at a basic rebase and then we’ll check out how to move a branch back to an earlier commit. <\/p>\n\n\n\n

Visualizing the Repo<\/h3>\n\n\n\n
git log --graph --all<\/code><\/pre>\n\n\n\n
First things first, when starting out with git in general and rebase more specifically, it’s really helpful to be able to checkout visual graph representation of the git repo.  Above is a command you can use to get just that. There are a ton of ways to format the log with a graph and if you’re interested in customizing it, you can checkout this article<\/a> for an overview and the answers to this post<\/a> if you want to make each commit only take up one line. I definitely recommend taking a look at this explanation<\/a> of how to create aliases as well that way you can save your fancy customized graph preferences in an easy to remember command.<\/p>\n\n\n\n
Basic Rebase Operation<\/h3>\n\n\n\n
A word of caution, it’s best not to rebase on branches or main that other folks are working on unless you have a specific plan or workflow everyone has agreed upon. This is because a rebase will not only change the base of the commits or branch being moved, but rebasing will change the hash (alpha numeric string associated with the commit) of the commits that are being moved.<\/strong><\/p>\n\n\n\n
Before we begin, just like a merge you can abort a rebase at any time before it’s complete by using the abort flag:<\/p>\n\n\n\n
git rebase --abort<\/code><\/pre>\n\n\n\n
If you use the commands:<\/p>\n\n\n\n
git checkout topic\ngit rebase main<\/code><\/pre>\n\n\n\n
Or the command:<\/p>\n\n\n\n
git rebase main topic<\/code><\/pre>\n\n\n\n
It will take your repo from this:<\/p>\n\n\n\n
topic:           E - F\n               \/\nmain: A - B - C - D<\/code><\/pre>\n\n\n\n
To this:<\/p>\n\n\n\n
A - B - C - D - E<\/strong> - F<\/strong> - G<\/strong> \n            |   |       |\n            |   |       topic branch stops\n            |   topic branch starts\n            main stops\n\nE, F and G have new hashes <\/strong><\/code><\/pre>\n\n\n\n
If there are conflicts you will need to manually go into the files and decide what to keep in the files with conflicts (the first resolution will be any conflicts between D and E).  If not you’ll, be able to skip ahead to the next steps section.<\/p>\n\n\n\n
When you resolve all the conflicts for the first commit, in this case E, you’ll need these two commands:<\/p>\n\n\n\n
git add .\ngit rebase --continue<\/code><\/pre>\n\n\n\n
You’ll have to repeat the resolve conflicting files, add resolved files, and rebase continue process for each commit.  In our example, we would repeat it for F and G.<\/p>\n\n\n\n
Next Steps<\/strong><\/p>\n\n\n\n
In most situations, you’ll want to do two additional steps after the rebase is complete.<\/p>\n\n\n\n
Merge the topic branch into main:<\/p>\n\n\n\n
git checkout main\ngit merge topic<\/code><\/pre>\n\n\n\n
Resulting in:<\/p>\n\n\n\n
A - B - C - D - E - F - G\n                        |\n                        main AND topic end<\/code><\/pre>\n\n\n\n
Remove the topic branch:<\/p>\n\n\n\n
git branch -d topic<\/code><\/pre>\n\n\n\n
Finally, we arrive here with a single branch on main:<\/p>\n\n\n\n
main: A - B - C - D - E - F - G<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
Rebasing a Branch on a Previous Commit<\/h3>\n\n\n\n
This word of caution is worth mentioning again. It’s best not to rebase on branches or main that other folks are working on unless you have a specific plan or workflow everyone has agreed upon. This is because a rebase will not only change the base of the commits or branch being moved, but rebasing will change the hash (alpha numeric string associated with the commit) of the commits that are being moved.<\/strong><\/p>\n\n\n\n
Now that we are very clear on that, say we have this situation:<\/p>\n\n\n\n
topic:              E - F\n                   \/\nmain: A - B - C - D<\/code><\/pre>\n\n\n\n
And we want this to be our end result:<\/p>\n\n\n\n
topic:      E - F\n           \/\nmain: A - B - C - D<\/code><\/pre>\n\n\n\n
It is very similar to a basic rebase.  You will just need the hash of the commit you want to move the branch to.  In this case commit B:<\/p>\n\n\n\n
git checkout topic\ngit rebase --onto hash_of_B main<\/code><\/pre>\n\n\n\n
or<\/p>\n\n\n\n
git rebase main topic --onto hash_of_B<\/code><\/pre>\n\n\n\n
If you want to make sure you’re moving the intended commits, you can use the interactive mode by adding an -i flag:<\/p>\n\n\n\n
git rebase main -i topic --onto hash_of_B<\/code><\/pre>\n\n\n\n
Like it was described for the basic merge, you will need to cycle through the commits resolving any conflicts and using the commands:<\/p>\n\n\n\n
git add .\ngit rebase --continue<\/code><\/pre>\n\n\n\n
Once all of the conflicts are resolved and the rebase is complete, we will arrive to our destination:<\/p>\n\n\n\n
topic:      E - F\n           \/\nmain: A - B - C - D<\/code><\/pre>\n\n\n\n
Root Included Variation<\/strong><\/p>\n\n\n\n
If you wanted to include the root in the rebase option to get this:<\/p>\n\n\n\n
topic:      D - E - F\n           \/\nmain: A - B - C<\/code><\/pre>\n\n\n\n
You would use the root flag:<\/p>\n\n\n\n
git checkout topic\ngit rebase --onto hash_of_B --root main<\/code><\/pre>\n\n\n\n
In Conclusion<\/h3>\n\n\n\n
These are a couple basic rebase commands.  Rebase can do quite a few things.  I also recommend checking out the squash feature<\/a>, if you don’t know it already.  It is very useful for those times you realize you missed something in your commit and you have to commit again.  It allows you to make one commit out of multiple commits.<\/p>\n\n\n\n
Until next post, be a goldfish.<\/p>\n\n\n\n
Sources<\/h3>\n\n\n\n