summaryrefslogtreecommitdiff
path: root/_posts/2010-01-29-rebase.markdown
diff options
context:
space:
mode:
authorCameron McEfee <cameron@github.com>2011-05-16 14:07:48 -0700
committerCameron McEfee <cameron@github.com>2011-05-16 16:55:31 -0700
commita483a05335c753555aba8c4529a62eb50b470028 (patch)
tree13309e7ff7b36f6020390e19067ff2251e26456d /_posts/2010-01-29-rebase.markdown
parentb9e8a41be8370615b233e01da697d1e6cba0b3f6 (diff)
Update files to match new style guide
Diffstat (limited to '_posts/2010-01-29-rebase.markdown')
-rw-r--r--_posts/2010-01-29-rebase.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2010-01-29-rebase.markdown b/_posts/2010-01-29-rebase.markdown
index 8fce0f6..40539cf 100644
--- a/_posts/2010-01-29-rebase.markdown
+++ b/_posts/2010-01-29-rebase.markdown
@@ -5,7 +5,7 @@ description: Using git rebase to restructure a branch
categories: everyday_git
---
-One often overlooked feature of git is the `git rebase` command. Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit.
+<p class="intro">One often overlooked feature of git is the <code>git rebase</code> command. Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit.</p>
<span class="attention">It is considered bad practice to rebase commits which you have already pushed to a remote repo. Doing so may invoke the wrath of the git gods... you have been warned.</span>