{"id":355658,"date":"2021-11-12T07:16:24","date_gmt":"2021-11-12T15:16:24","guid":{"rendered":"https:\/\/css-tricks.com\/?p=355658"},"modified":"2021-12-03T07:49:23","modified_gmt":"2021-12-03T15:49:23","slug":"interactive-rebase-clean-up-your-commit-history","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/interactive-rebase-clean-up-your-commit-history\/","title":{"rendered":"Interactive Rebase: Clean up your Commit History"},"content":{"rendered":"\n<p class=\"is-style-explanation\">This article is part of our <a href=\"https:\/\/css-tricks.com\/creating-the-perfect-commit-in-git\/\">\u201cAdvanced Git\u201d<\/a> series. Be sure to <a href=\"https:\/\/twitter.com\/gittower\" rel=\"noopener\">follow Tower on Twitter<\/a> or <a href=\"https:\/\/www.git-tower.com\/newsletter\" rel=\"noopener\">sign up for their newsletter<\/a> to hear about the next articles.<\/p>\n\n\n\n<p>Interactive Rebase is the Swiss Army knife of Git commands: lots of use cases and lots of possibilities! It&#8217;s really a great addition to any developer&#8217;s tool chain, because it lets you revise your local commit history\u2014before you share your work with the rest of the team.<\/p>\n\n\n\n<p>Let&#8217;s see what you can do with an interactive rebase and then look at some practical examples.<\/p>\n\n\n\n<!--more-->\n\n\n\n<div class=\"wp-block-group ticss-c35bb282\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\"><h4 class=\"wp-block-heading\" id=\"h-advanced-git-series\">Advanced Git series:<\/h4>\n\n\n<ol><li><strong>Part 1:<\/strong> <a href=\"\/creating-the-perfect-commit-in-git\"><\/a><a href=\"https:\/\/css-tricks.com\/creating-the-perfect-commit-in-git\/\">Creating the Perfect Commit in Git<\/a><\/li><li><strong>Part 2:<\/strong> <a href=\"https:\/\/css-tricks.com\/branching-strategies-in-git\/\">Branching Strategies in Git<\/a><\/li><li><strong>Part 3:<\/strong> <a href=\"https:\/\/css-tricks.com\/better-collaboration-with-pull-requests\/\">Better Collaboration With Pull Requests<\/a><\/li><li><strong>Part 4:<\/strong> <a href=\"https:\/\/css-tricks.com\/merge-conflicts-what-they-are-and-how-to-deal-with-them\">Merge Conflicts<\/a><\/li><li><strong>Part 5:<\/strong> <a href=\"https:\/\/css-tricks.com\/rebase-vs-merge-integrating-changes-in-git\">Rebase vs. Merge<\/a><\/li><li><strong>Part 6:<\/strong> <a href=\"https:\/\/css-tricks.com\/interactive-rebase-clean-up-your-commit-history\">Interactive Rebase<\/a> (<em>You are here!<\/em>)<\/li><li><strong>Part 7:<\/strong> <a href=\"https:\/\/css-tricks.com\/cherry-picking-commits-in-git\">Cherry-Picking Commits in Git<\/a><\/li><li><strong>Part 8:<\/strong> <a href=\"https:\/\/css-tricks.com\/using-the-reflog-to-restore-lost-commits\/\">Using the Reflog to Restore Lost Commits<\/a><\/li><\/ol>\n\n\n\n<p><\/p>\n<\/div><\/div>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-rewriting-your-commit-history\">Rewriting your commit history<\/h3>\n\n\n<p>In short, interactive rebase allows you to manipulate your commit history. It&#8217;s meant for optimizing and cleaning up. You can&#8230;<\/p>\n\n\n\n<ul><li>change commit messages<\/li><li>combine multiple commits<\/li><li>split and edit existing commits<\/li><li>reorder commits<\/li><li>delete commits<\/li><\/ul>\n\n\n\n<p>Keep in mind that an interactive rebase rewrites your commit history: all of the involved commits get a new hash ID. Also, a quick reminder: commit IDs are there to identify commits\u2014they are SHA-1 checksums. So, by changing that hash, you technically create completely new commits. This means that you shouldn\u2019t use an interactive rebase on stuff that you\u2019ve already pushed to a shared remote repository. Your colleagues might have based their work on these commits\u2014and when you use interactive rebase to rewrite commit history, you are changing these base commits.<\/p>\n\n\n\n<p>All of this means that an interactive rebase is meant to help you clean up and optimize your own local commit history before you merge (and possibly push) it back into a shared team branch.<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-interactive-rebase-workflow\">Interactive rebase workflow<\/h3>\n\n\n<p>Before we take interactive rebase for a test drive, let&#8217;s look at the general workflow. This is always the same, no matter what exactly we&#8217;re doing\u2014deleting a commit, changing a commit message, combining commits&#8230; the steps are identical.<\/p>\n\n\n\n<p>The first step is to determine the range of commits you want to manipulate. How far back in time do you want to go? Once you have the answer, you can start your interactive rebase session. Here, you have the chance to edit your commit history. For example, you can manipulate the selected commits by reordering, deleting, combining them, and so on.<\/p>\n\n\n\n<p>In your first step, you are always going to look at the current state of the commit history. You can use the <code>git log<\/code> command to examine a project&#8217;s history and show the commit log.<\/p>\n\n\n\n<p>Here\u2019s the little example repository we\u2019re going to use throughout this article:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1190\" height=\"912\" src=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?resize=1190%2C912&#038;ssl=1\" alt=\"Showing a Git Tower app screen with the main master branch of a repo selected on the left panel, and a list of existing commits on the right panel.\" class=\"wp-image-355660\" srcset=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?w=1190&amp;ssl=1 1190w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?resize=300%2C230&amp;ssl=1 300w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?resize=1024%2C785&amp;ssl=1 1024w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?resize=768%2C589&amp;ssl=1 768w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/commit-history_example-scenario@2x.png?resize=1000%2C766&amp;ssl=1 1000w\" sizes=\"(min-width: 735px) 864px, 96vw\" data-recalc-dims=\"1\" \/><figcaption>Note that I\u2019m using the <a href=\"https:\/\/www.git-tower.com\/?utm_source=csstricks&amp;utm_medium=guestpost&amp;utm_campaign=interactive-rebase\" rel=\"noopener\">Tower Git desktop GUI<\/a> in some of my screenshots for easier visualization.<\/figcaption><\/figure>\n\n\n\n<p>After you&#8217;ve examined the list, it&#8217;s time to start the work. Let&#8217;s do this step-by-step. In the examples of this article, we will do the following things:<\/p>\n\n\n\n<ul><li>First, we change an old commit&#8217;s message.<\/li><li>Secondly, we combine two old commits.<\/li><li>After that, we split one commit.<\/li><li>Finally, we delete a commit.<\/li><\/ul>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-change-a-commit-message\">Change a commit message<\/h2>\n\n\n<p>In many cases, you\u2019ll want to change the most recent commit. Keep in mind that there\u2019s a shortcut for this scenario which doesn\u2019t involve interactive rebase:<\/p>\n\n\n\n<pre rel=\"Terminal\" class=\"wp-block-csstricks-code-block language-none\" data-line=\"\"><code markup=\"tt\">$ git commit --amend<\/code><\/pre>\n\n\n\n<p>This command can modify both the content and the message of the most recent commit, and it opens your default text editor. Here you can make your changes, save them, and quit the editor. This will not only update the commit message, but will effectively change the commit itself and write a new one.<\/p>\n\n\n\n<p>Again, <em>please be careful<\/em> and don&#8217;t amend your last commit if you&#8217;ve already pushed it to the remote repository!<\/p>\n\n\n\n<p>For any other commit (anything older than the most recent one), you have to perform an interactive rebase. To run <code>git rebase<\/code> interactively, add the <code>-i<\/code> option.&nbsp;<\/p>\n\n\n\n<p>The first step is to determine the base commit: the parent commit of the one you want to change. You can achieve this by using the commit&#8217;s hash ID or by doing a little bit of counting. To change the last three commit messages (or at least one of them), you can define the parent commit like this:<\/p>\n\n\n\n<pre rel=\"Terminal\" class=\"wp-block-csstricks-code-block language-none\" data-line=\"\"><code markup=\"tt\">$ git rebase -i HEAD~3<\/code><\/pre>\n\n\n\n<p>An editor window opens and you can see all three commits you selected (and by \u201cselected\u201d I mean a range of commits: from <code>HEAD<\/code> all the way down to <code>HEAD~3<\/code>). Please notice the reverse order: unlike <code>git log<\/code>, this editor shows the oldest commit (<code>HEAD~3<\/code>) at the top and the newest at the bottom.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"700\" height=\"370\" src=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/interactive-rebase_reword_CLI.gif?resize=700%2C370&#038;ssl=1\" alt=\"Animated screenshot showing an open terminal that edits the commit and adds a reword command on another line.\" class=\"wp-image-355662\" data-recalc-dims=\"1\"\/><\/figure>\n\n\n\n<p>In this window you <em>don&#8217;t<\/em> actually change the commit message. You only <em>tell<\/em> Git <em>what kind of manipulation<\/em> you want to perform. Git offers a series of keywords for this\u2014in our case, we change the word <code>pick<\/code> to <code>reword<\/code> which allows us to change the commit messages. After saving and closing the editor, Git will show the actual commit message and you can change it. Save and exit again, that&#8217;s it!<\/p>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-combining-two-commits\">Combining two commits<\/h3>\n\n\n<p>In this next example, we\u2019ll combine the two commits\u2014\u201c7b2317cf Change the page structure\u201d and \u201c6bcf266 Optimize markup\u201d\u2014so that they become one single commit. Again, as a first step you need to determine the base commit. And again, we have to go back to <em>at least<\/em> the parent commit:<\/p>\n\n\n\n<pre rel=\"Terminal\" class=\"wp-block-csstricks-code-block language-none\" data-line=\"\"><code markup=\"tt\">$ git rebase -i HEAD~3<\/code><\/pre>\n\n\n\n<p>The editor window opens again, but instead of <code>reword<\/code>, we\u2019ll enter <code>squash<\/code>. To be exact, we replace <code>pick<\/code> with <code>squash<\/code> in line 2 to combine it with line 1. This is an important bit to keep in mind: the <code>squash<\/code> keyword combines the line you mark up with the line <strong>above<\/strong> it!<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1388\" height=\"660\" src=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?resize=1388%2C660&#038;ssl=1\" alt=\"Showing an open terminal with a squash on line 2 and giants words in red pointing to that line saying that squash combines the marked up line with the line above it.\" class=\"wp-image-355667\" srcset=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?w=1388&amp;ssl=1 1388w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?resize=300%2C143&amp;ssl=1 300w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?resize=1024%2C487&amp;ssl=1 1024w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?resize=768%2C365&amp;ssl=1 768w, https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-editor@2x.png?resize=1000%2C476&amp;ssl=1 1000w\" sizes=\"(min-width: 735px) 864px, 96vw\" data-recalc-dims=\"1\" \/><\/figure>\n\n\n\n<p>After saving the changes and closing the window, a new editor window pops up. Why&#8217;s that? By combining two commits we are creating&#8230; well&#8230; a new commit! And this new commit wants a commit message. Enter the message, save and close the window\u2026 and you&#8217;ve successfully combined the two commits. Powerful stuff!<\/p>\n\n\n\n<p>Finally a little \u201cpro tip\u201d for those of you working with the <a href=\"https:\/\/www.git-tower.com\/?utm_source=csstricks&amp;utm_medium=guestpost&amp;utm_campaign=interactive-rebase\" rel=\"noopener\">\u201cTower\u201d Git desktop GUI<\/a>: to perform a squash, you can simply drag and drop commits onto each other, right in the commits view. And if you want to change a commit message, simply right click the commit in question and select \u201cEdit commit message\u201d from the contextual menu.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"700\" height=\"544\" src=\"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/squash-in-tower.gif?resize=700%2C544&#038;ssl=1\" alt=\"Animated screenshot showing the process of dragging one commit message on top of another, squashing the message, then editing the commit message.\" class=\"wp-image-355670\" data-recalc-dims=\"1\"\/><\/figure>\n\n\n<h3 class=\"wp-block-heading\" id=\"h-deleting-a-commit\">Deleting a commit<\/h3>\n\n\n<p>We\u2019re bringing in the big guns for our final example: we are going to <em>delete<\/em> a revision from our commit history! To do this, we\u2019re using the <code>drop<\/code> keyword to mark up the commit we want to get rid of:<\/p>\n\n\n\n<pre rel=\"Terminal\" class=\"wp-block-csstricks-code-block language-none\" data-line=\"\"><code markup=\"tt\">drop 0023cdd Add simple robots.txt\npick 2b504be Change headlines for about and imprint\npick 6bcf266 Optimizes markup structure in index page<\/code><\/pre>\n\n\n\n<p>This is probably a good moment to answer a question you might have had for some time now: what can you do if you&#8217;re in the middle of a rebase operation and think, \u201cOh, no, this wasn&#8217;t such a good idea after all\u201d? No problem\u2014you can always abort! Just enter the following command to turn back to the state your repository was in before you initiated the rebase:<\/p>\n\n\n\n<pre rel=\"Terminal\" class=\"wp-block-csstricks-code-block language-none\" data-line=\"\"><code markup=\"tt\">$ git rebase --abort<\/code><\/pre>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-changing-the-past\">Changing the past<\/h2>\n\n\n<p>These were just a few examples of what an interactive rebase can do. There are plenty of other possibilities to control and revise your local commit history.<\/p>\n\n\n\n<p>If you want to dive deeper into advanced Git tools, feel free to check out my (free!)<a href=\"https:\/\/www.git-tower.com\/learn\/git\/advanced-git-kit?utm_source=csstricks&amp;utm_medium=guestpost&amp;utm_campaign=interactive-rebase\" rel=\"noopener\"> \u201cAdvanced Git Kit\u201d<\/a>: it\u2019s a collection of short videos about topics like branching strategies, Interactive Rebase, Reflog, Submodules and much more.<\/p>\n\n\n\n<p>Happy rebasing and hacking\u2014and see you soon for the next part in our series on \u201cAdvanced Git\u201d!<\/p>\n\n\n\n<div class=\"wp-block-group ticss-c35bb282\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\"><h4 class=\"wp-block-heading\" id=\"h-advanced-git-series-1\">Advanced Git series:<\/h4>\n\n\n<ol><li><strong>Part 1:<\/strong> <a href=\"\/creating-the-perfect-commit-in-git\"><\/a><a href=\"https:\/\/css-tricks.com\/creating-the-perfect-commit-in-git\/\">Creating the Perfect Commit in Git<\/a><\/li><li><strong>Part 2:<\/strong> <a href=\"https:\/\/css-tricks.com\/branching-strategies-in-git\/\">Branching Strategies in Git<\/a><\/li><li><strong>Part 3:<\/strong> <a href=\"https:\/\/css-tricks.com\/better-collaboration-with-pull-requests\/\">Better Collaboration With Pull Requests<\/a><\/li><li><strong>Part 4:<\/strong> <a href=\"https:\/\/css-tricks.com\/merge-conflicts-what-they-are-and-how-to-deal-with-them\">Merge Conflicts<\/a><\/li><li><strong>Part 5:<\/strong> <a href=\"https:\/\/css-tricks.com\/rebase-vs-merge-integrating-changes-in-git\">Rebase vs. Merge<\/a><\/li><li><strong>Part 6:<\/strong> <a href=\"https:\/\/css-tricks.com\/interactive-rebase-clean-up-your-commit-history\">Interactive Rebase<\/a> (<em>You are here!<\/em>)<\/li><li><strong>Part 7:<\/strong> <a href=\"https:\/\/css-tricks.com\/cherry-picking-commits-in-git\">Cherry-Picking Commits in Git<\/a><\/li><li><strong>Part 8:<\/strong> <a href=\"https:\/\/css-tricks.com\/using-the-reflog-to-restore-lost-commits\/\">Using the Reflog to Restore Lost Commits<\/a><\/li><\/ol>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Interactive Rebase is the Swiss Army knife of Git commands: lots of use cases and lots of possibilities! It&#8217;s really a great addition to any developer&#8217;s tool chain, because it lets you revise your local commit history\u2014before you share your work with the rest of the team. Let&#8217;s see what you can do with an interactive rebase and then look at some practical examples.<\/p>\n","protected":false},"author":247217,"featured_media":355662,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"sig_custom_text":"","sig_image_type":"featured-image","sig_custom_image":0,"sig_is_disabled":false,"inline_featured_image":false,"c2c_always_allow_admin_comments":false,"footnotes":"","jetpack_publicize_message":"Interactive Rebase: Clean up your Commit History by @gntr","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":[]},"categories":[4],"tags":[766,18993],"jetpack_publicize_connections":[],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/interactive-rebase_reword_CLI.gif?fit=700%2C370&ssl=1","jetpack-related-posts":[{"id":354734,"url":"https:\/\/css-tricks.com\/rebase-vs-merge-integrating-changes-in-git\/","url_meta":{"origin":355658,"position":0},"title":"Rebase vs. Merge: Integrating Changes in Git","date":"November 2, 2021","format":false,"excerpt":"This article is part of our \u201cAdvanced Git\u201d series. Be sure to follow us on Twitter or sign up for our newsletter to hear about the next articles! Most developers understand that it's important to use branches in Git. In fact, I've written an entire article on branching strategies in\u2026","rel":"","context":"In &quot;Article&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/10\/rebase-git.jpg?fit=1200%2C600&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":356700,"url":"https:\/\/css-tricks.com\/cherry-picking-commits-in-git\/","url_meta":{"origin":355658,"position":1},"title":"Cherry-Picking Commits in Git","date":"November 17, 2021","format":false,"excerpt":"In part 5 of this series, we looked at rebasing and merging. Although there are a couple of differences between git merge and git rebase, both commands have the same goal: they integrate changes from one branch into another.","rel":"","context":"In &quot;Article&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/git-cherry-picking.png?fit=1200%2C600&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":316153,"url":"https:\/\/css-tricks.com\/cmdz-for-git-is-here\/","url_meta":{"origin":355658,"position":2},"title":"CMD+Z for Git is Here","date":"July 23, 2020","format":false,"excerpt":"Version control with Git has become a \"commodity\" by now: virtually every software project today uses Git, and virtually every developer knows Git to some extent. This explains why I sometimes hear the following question when I talk about what I do for a living: \"A desktop client for Git?\u2026","rel":"","context":"In &quot;Sponsored&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2020\/07\/tower_testimonials@2x.png?fit=1200%2C550&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":354389,"url":"https:\/\/css-tricks.com\/merge-conflicts-what-they-are-and-how-to-deal-with-them\/","url_meta":{"origin":355658,"position":3},"title":"Merge Conflicts: What They Are and How to Deal with Them\u200b","date":"October 28, 2021","format":false,"excerpt":"Merge conflicts... Nobody likes them. Some of us even fear them. But they are a fact of life when you're working with Git, especially when you're teaming up with other developers. In most cases, merge conflicts aren't as scary as you might think. In this fourth part of our \u201cAdvanced\u2026","rel":"","context":"In &quot;Article&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/10\/conflict-in-textfile@2x.png?fit=1130%2C622&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":357728,"url":"https:\/\/css-tricks.com\/using-the-reflog-to-restore-lost-commits\/","url_meta":{"origin":355658,"position":4},"title":"Using the Reflog to Restore Lost Commits","date":"November 30, 2021","format":false,"excerpt":"This article is part of our \u201cAdvanced Git\u201d series. Be sure to follow us on Twitter or sign up for our newsletter to hear about future articles! The \u201cReflog\u201d is one of Git\u2019s lesser-known features\u2014but one that can be extremely helpful. Some people refer to it as a \u201csafety net,\u201d\u2026","rel":"","context":"In &quot;Article&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/11\/pasted-image-0-2.png?fit=1200%2C438&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]},{"id":352569,"url":"https:\/\/css-tricks.com\/better-collaboration-with-pull-requests\/","url_meta":{"origin":355658,"position":5},"title":"Better Collaboration With Pull Requests","date":"October 11, 2021","format":false,"excerpt":"This article is part of our \u201cAdvanced Git\u201d series. Be sure to follow us on Twitter or sign up for our newsletter to hear about the next articles! In this third installment of our \u201cAdvanced Git\u201d series, we\u2019ll look at pull requests \u2014 a great feature which helps both small\u2026","rel":"","context":"In &quot;Article&quot;","img":{"alt_text":"","src":"https:\/\/i0.wp.com\/css-tricks.com\/wp-content\/uploads\/2021\/09\/Untitled-3-2.png?fit=1200%2C375&ssl=1&resize=350%2C200","width":350,"height":200},"classes":[]}],"_links":{"self":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/355658"}],"collection":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/users\/247217"}],"replies":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/comments?post=355658"}],"version-history":[{"count":10,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/355658\/revisions"}],"predecessor-version":[{"id":358353,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/posts\/355658\/revisions\/358353"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/media\/355662"}],"wp:attachment":[{"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/media?parent=355658"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/categories?post=355658"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/css-tricks.com\/wp-json\/wp\/v2\/tags?post=355658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}