diff options
| author | Cameron McEfee <cameron@github.com> | 2011-02-28 14:26:03 -0800 |
|---|---|---|
| committer | Cameron McEfee <cameron@github.com> | 2011-02-28 14:26:03 -0800 |
| commit | 9daf8363660584647d2c38f5b1ce7c664db1d5cb (patch) | |
| tree | 389e49ee827fd235e9f255ccc325f3f696c3b8e7 /_posts/2011-02-15-win-set-up-git.markdown | |
| parent | 57c3a33ebf173f06fe2e206c0dc3a2cf9aac3b4b (diff) | |
added more definitions/explanations
Diffstat (limited to '_posts/2011-02-15-win-set-up-git.markdown')
| -rw-r--r-- | _posts/2011-02-15-win-set-up-git.markdown | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/_posts/2011-02-15-win-set-up-git.markdown b/_posts/2011-02-15-win-set-up-git.markdown index 3317093..2db5d8d 100644 --- a/_posts/2011-02-15-win-set-up-git.markdown +++ b/_posts/2011-02-15-win-set-up-git.markdown @@ -4,7 +4,7 @@ title: Set Up Git (Windows) description: A quick guide to help you get started with Git --- -<span class="intro">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 setting both up, and explain a little about how everything works along the way. If you already have Git experience and just want the short version, read the <a href="http://help.github.com">technical walkthrough instead</a>.</span> +<span class="intro">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.</span> ##<span>First:</span> Download and Install Git @@ -40,14 +40,14 @@ To make sure you generate a brand new key, you need to check if one already exis <div class="more-info"> <h4 class="compressed">Need a quick lesson about Git Bash?</h4> <div class="more-content"> - <p>Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that comes with Linux called Terminal.</p> + <p>Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that was installed with Git called Git Bash.</p> <h4>Input</h4> <pre class="terminal bootcamp"> <span class="codeline">$ echo 'This is input text'<span>This tooltip tells you what's going on.</span></span> </pre> - <p>A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing</p> + <p>A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing.</p> <h4>Output</h4> <pre class="terminal bootcamp"> @@ -58,12 +58,12 @@ To make sure you generate a brand new key, you need to check if one already exis <h4>User Specific Input</h4> <pre class="terminal bootcamp"> - <span class="codeline">$ echo '<em>username</em>'<span>Outputs the text in the quote marks.</span></span> + <span class="codeline">$ echo '<em>username</em>'<span>Outputs the text in the quotation marks.</span></span> </pre> - <p>Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace your it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Git Bash</p> + <p>Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Git Bash.</p> - <p><strong>Good to know</strong>: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in the Git Bash don’t have any output. Don’t worry, if there is ever a problem with your code, Git Bash will let you know.</p> + <p><strong>Good to know</strong>: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Git Bash don’t have any output. Don’t worry, if there is ever a problem with your code, Git Bash will let you know.</p> <p><strong>Good to know</strong>: For security reasons, Git Bash will not display what you type when entering passwords. Just type your password and hit the return key.</p> </div> @@ -81,12 +81,12 @@ To make sure you generate a brand new key, you need to check if one already exis 2. <span class="step-title">Backup and remove existing SSH keys.</span> - Since there is already an SSH directory you’ll want to back it up and remove it: + Since there is already an SSH directory you’ll want to back the old one up and remove it: <pre class="terminal bootcamp"> <span class="codeline">$ ls<span>Lists all the subdirectories in the current directory</span></span> <span class="bash-output">config id_rsa id_rsa.pub known_hosts</span> - <span class="codeline">$ mkdir key_backup<span>Makes a directory called "key_backup" in the current directory</span></span> + <span class="codeline">$ mkdir key_backup<span>makes a subdirectory called "key_backup" in the current directory</span></span> <span class="codeline">$ cp id_rsa* key_backup<span>Copies the contents of the id_rsa directory into key_backup directory</span></span> <span class="codeline">$ rm id_rsa*<span>Deletes the contents of the id_rsa directory</span></span> </pre> @@ -134,7 +134,7 @@ To make sure you generate a brand new key, you need to check if one already exis On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_ - First, open the id_rsa.pub file with a text editor (Notepad will do just fine). This is your SSH key. __It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ Now paste it into the “Key” field. + Open the id_rsa.pub file with a text editor (Notepad will do just fine). This is your SSH key. __It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ Now paste it into the “Key” field. <img src="/images/bootcamp/bootcamp_1_ssh.jpg" width="558" height="402" alt="Paste your SSH Key" /> @@ -165,11 +165,11 @@ To make sure you generate a brand new key, you need to check if one already exis </pre> - Don’t worry, about the “failed” part. All you should about is that you see “You’ve successfully authenticated” + Don’t worry, about the “failed” part. All you should care about is that you see “You’ve successfully authenticated” ##<span>Then: </span> Set Up Your Info -Now that you have Git set up and your SSH keys entered in GitHub, it’s time to configure your personal info. +Now that you have Git set up and your SSH keys entered into GitHub, it’s time to configure your personal info. 1. <span class="step-title">Set your username and email.</span> |