From 2575b8a597d3febb0088d02fb64214c3dbd5fd57 Mon Sep 17 00:00:00 2001 From: Cameron McEfee Date: Mon, 16 May 2011 10:23:11 -0700 Subject: bring documentation in line with new styles --- _posts/2008-02-16-create-a-repo.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to '_posts/2008-02-16-create-a-repo.markdown') diff --git a/_posts/2008-02-16-create-a-repo.markdown b/_posts/2008-02-16-create-a-repo.markdown index ecfc3fe..1f43a75 100644 --- a/_posts/2008-02-16-create-a-repo.markdown +++ b/_posts/2008-02-16-create-a-repo.markdown @@ -7,7 +7,7 @@ categories: bootcamp If you’ve found yourself on this page, we’re assuming you’re brand new to Git and GitHub. This guide will walk you through the basics and explain a little bit about how everything works along the way. -##First: Create A Repo +##First: Create A Repo Every time you make a commit with Git, it is stored in a repository (a.k.a. “repo”). To put your project up on GitHub, you’ll need to have a GitHub repository for it to live in. @@ -32,7 +32,7 @@ Every time you make a commit with Git, it is stored in a repository (a.k.a. &ldq Congratulations! You have successfully created your first repo! -##Next: Create a README for your repo. +##Next: Create a README for your repo. While a README isn’t a required part of a GitHub repo, it is a good idea to have one. READMEs are a great place to describe your project or add some documentation such as how to install or use your project. @@ -101,7 +101,7 @@ While a README isn’t a required part of a GitHub repo, it is a good idea t Your README has been created -##Lastly: Celebrate +##Lastly: Celebrate Congratulations! You have now created a repository on GitHub, created a README, committed it, and pushed it to GitHub. What do you want to do next? -- cgit v1.3.1