diff options
| -rw-r--r-- | _posts/2011-02-15-linux-set-up-git.markdown | 81 | ||||
| -rw-r--r-- | _posts/2011-02-15-mac-set-up-git.markdown | 27 | ||||
| -rw-r--r-- | _posts/2011-02-15-win-set-up-git.markdown | 79 | ||||
| -rw-r--r-- | _posts/2011-02-16-create-a-repo.markdown | 10 | ||||
| -rw-r--r-- | _posts/2011-02-17-fork-a-repo.markdown | 25 | ||||
| -rw-r--r-- | _posts/2011-02-18-be-social.markdown | 12 | ||||
| -rwxr-xr-x | css/style.css | 92 |
7 files changed, 135 insertions, 191 deletions
diff --git a/_posts/2011-02-15-linux-set-up-git.markdown b/_posts/2011-02-15-linux-set-up-git.markdown index 8b58ae6..0450529 100644 --- a/_posts/2011-02-15-linux-set-up-git.markdown +++ b/_posts/2011-02-15-linux-set-up-git.markdown @@ -34,46 +34,44 @@ To make sure you generate a brand new key, you need to check if one already exis <img src="/images/bootcamp/bootcamp_1_linux_terminal.jpg" width="558" height="328" alt="Open the terminal" /> -<span class="explain">Need a quick lesson about Terminal? - <span class="explain-it-shell"> - <span class="triangle"> </span> - <span class="explain-it"> - <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> - - <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 to see what the script is doing</p> - - <h4>Output</h4> - <pre class="terminal bootcamp"> - <span class="bash-output">$ This is output text.</span> - </pre> - - <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We've colored output text green in these bootcamp tutorials.</p> - - <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> - </pre> - - <p>Areas of yellow text represent your own personal info. 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 Terminal</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 Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.</p> +<div class="more-info"> + <h4 class="compressed">Need a quick lesson about Terminal?</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 your Mac called Terminal.</p> - <p><strong>Good to know</strong>: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.</p> - </span> - </span> -</span> + <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> + + <h4>Output</h4> + <pre class="terminal bootcamp"> + <span class="bash-output">$ This is output text.</span> + </pre> + + <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.</p> + + <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> + </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 Terminal</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 Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.</p> + + <p><strong>Good to know</strong>: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.</p> + </div> +</div> 1. <span class="step-title">Check for SSH keys. <span>Have an existing kepair? You can skip to Step 4.</span></span> First, we need to check for existing ssh keys on your computer: <pre class="terminal bootcamp"> - <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a folder named ".ssh" in you user directory</span></span> + <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a directory named ".ssh" in your user directory</span></span> </pre> If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__. @@ -85,9 +83,9 @@ To make sure you generate a brand new key, you need to check if one already exis <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 folder 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 folder into key_backup folder</span></span> - <span class="codeline">$ rm id_rsa*<span>Deletes the contents of the id_rsa folder</span></span> + <span class="codeline">$ mkdir key_backup<span>Makes a directory 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> 3. <span class="step-title">Generate a new SSH key.</span> @@ -136,7 +134,7 @@ To make sure you generate a brand new key, you need to check if one already exis <pre class="terminal bootcamp"> <span class="codeline">$ sudo apt-get install xclip<span>Downloads and installs xclip</span></span> - <span class="codeline">$ cat ~/.ssh/id_rsa.pub | xclip -sel clip<span>Copies the contents of the id_rsa.pub file to your clipboard</span></span> + <span class="codeline">$ xclip -sel clip < ~/.ssh/id_rsa.pub<span>Copies the contents of the id_rsa.pub file to your clipboard</span></span> </pre> Now paste it into the “Key” field. @@ -164,12 +162,13 @@ To make sure you generate a brand new key, you need to check if one already exis Don’t worry, this is supposed to happen. Type “yes”. <pre class="terminal bootcamp"> - <span class="bash-output">Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.</span> - <span class="bash-output">ERROR: Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide <br />shell access</span> + <span class="bash-output">PTY allocation request failed on channel 0</span> + <span class="bash-output">Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide shell access.</span> <span class="bash-output">Connection to github.com closed.</span> + </pre> - - You don’t worry, about the “ERROR”. You actually want to see that. + + Don’t worry, about the “failed” part. All you should about is that you see “You’ve successfully authenticated” ##<span>Then: </span> Set Up Your Info diff --git a/_posts/2011-02-15-mac-set-up-git.markdown b/_posts/2011-02-15-mac-set-up-git.markdown index a35e587..5cad08f 100644 --- a/_posts/2011-02-15-mac-set-up-git.markdown +++ b/_posts/2011-02-15-mac-set-up-git.markdown @@ -27,30 +27,30 @@ 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 Terminal?</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 comes with your Mac called Terminal.</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 to see 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"> <span class="bash-output">$ This is output text.</span> </pre> - <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We've colored output text green in these bootcamp tutorials.</p> + <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.</p> <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> </pre> - <p>Areas of yellow text represent your own personal info. 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 Terminal</p> + <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 Terminal</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 Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal 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 Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.</p> <p><strong>Good to know</strong>: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.</p> </div> @@ -61,7 +61,7 @@ To make sure you generate a brand new key, you need to check if one already exis First, we need to check for existing ssh keys on your computer: <pre class="terminal bootcamp"> - <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a folder named ".ssh" in you user directory</span></span> + <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a directory named ".ssh" in your user directory</span></span> </pre> If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__. @@ -73,9 +73,9 @@ To make sure you generate a brand new key, you need to check if one already exis <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 folder 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 folder into key_backup folder</span></span> - <span class="codeline">$ rm id_rsa*<span>Deletes the contents of the id_rsa folder</span></span> + <span class="codeline">$ mkdir key_backup<span>Makes a directory 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 </span></span> + <span class="codeline">$ rm id_rsa*<span>Deletes the contents of the id_rsa directory</span></span> </pre> 3. <span class="step-title">Generate a new SSH key.</span> @@ -123,7 +123,7 @@ To make sure you generate a brand new key, you need to check if one already exis __It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ To ensure this, run the following code to copy the key to your clipboard. <pre class="terminal bootcamp"> - <span class="codeline">$ cat ~/.ssh/id_rsa.pub | pbcopy<span>Copies the contents of the id_rsa.pub file to your clipboard</span></span> + <span class="codeline">$ pbcopy < ~/.ssh/id_rsa.pub<span>Copies the contents of the id_rsa.pub file to your clipboard</span></span> </pre> Now paste it into the “Key” field. @@ -151,12 +151,13 @@ To make sure you generate a brand new key, you need to check if one already exis Don’t worry, this is supposed to happen. Type “yes”. <pre class="terminal bootcamp"> - <span class="bash-output">Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.</span> - <span class="bash-output">ERROR: Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide <br />shell access</span> + <span class="bash-output">PTY allocation request failed on channel 0</span> + <span class="bash-output">Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide shell access.</span> <span class="bash-output">Connection to github.com closed.</span> + </pre> - You don’t worry, about the “ERROR”. You actually want to see that. + Don’t worry, about the “failed” part. All you should about is that you see “You’ve successfully authenticated” ##<span>Then: </span> Set Up Your Info diff --git a/_posts/2011-02-15-win-set-up-git.markdown b/_posts/2011-02-15-win-set-up-git.markdown index e1a8878..6d7db1a 100644 --- a/_posts/2011-02-15-win-set-up-git.markdown +++ b/_posts/2011-02-15-win-set-up-git.markdown @@ -37,46 +37,44 @@ To make sure you generate a brand new key, you need to check if one already exis <img src="/images/bootcamp/bootcamp_1_win_gitbash.jpg" width="558" height="300" alt="Open the terminal" /> -<span class="explain">Need a quick lesson about Terminal? - <span class="explain-it-shell"> - <span class="triangle"> </span> - <span class="explain-it"> - <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> - - <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 to see what the script is doing</p> - - <h4>Output</h4> - <pre class="terminal bootcamp"> - <span class="bash-output">$ This is output text.</span> - </pre> - - <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We've colored output text green in these bootcamp tutorials.</p> - - <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> - </pre> - - <p>Areas of yellow text represent your own personal info. 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 Terminal</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 Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.</p> +<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><strong>Good to know</strong>: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.</p> - </span> - </span> -</span> + <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> + + <h4>Output</h4> + <pre class="terminal bootcamp"> + <span class="bash-output">$ This is output text.</span> + </pre> + + <p>A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.</p> + + <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> + </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><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>: 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> +</div> 1. <span class="step-title">Check for SSH keys. <span>Have an existing kepair? You can skip to Step 4.</span></span> First, we need to check for existing ssh keys on your computer: <pre class="terminal bootcamp"> - <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a folder named ".ssh" in you user directory</span></span> + <span class="codeline">$ cd ~/.ssh<span>Checks to see if there is a directory named ".ssh" in your user directory</span></span> </pre> If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__. @@ -88,9 +86,9 @@ To make sure you generate a brand new key, you need to check if one already exis <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 folder 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 folder into key_backup folder</span></span> - <span class="codeline">$ rm id_rsa*<span>Deletes the contents of the id_rsa folder</span></span> + <span class="codeline">$ mkdir key_backup<span>Makes a directory 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> 3. <span class="step-title">Generate a new SSH key.</span> @@ -148,12 +146,13 @@ To make sure you generate a brand new key, you need to check if one already exis Don’t worry, this is supposed to happen. Type “yes”. <pre class="terminal bootcamp"> - <span class="bash-output">Warning: Permanently added 'github.com,207.97.227.239' (RSA) to the list of known hosts.</span> - <span class="bash-output">ERROR: Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide <br />shell access</span> + <span class="bash-output">PTY allocation request failed on channel 0</span> + <span class="bash-output">Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide shell access.</span> <span class="bash-output">Connection to github.com closed.</span> + </pre> - - You don’t worry, about the “ERROR”. You actually want to see that. + + Don’t worry, about the “failed” part. All you should about is that you see “You’ve successfully authenticated” ##<span>Then: </span> Set Up Your Info diff --git a/_posts/2011-02-16-create-a-repo.markdown b/_posts/2011-02-16-create-a-repo.markdown index ac8af10..cba62d8 100644 --- a/_posts/2011-02-16-create-a-repo.markdown +++ b/_posts/2011-02-16-create-a-repo.markdown @@ -33,14 +33,14 @@ While a README isn’t a required part of a GitHub repo, it is a good idea t In the prompt, type the following code: <pre class="terminal bootcamp"> - <span class="codeline">$ mkdir ~/Hello-World<span>Creates a folder for your project called "Hello-World" in your user folder</span></span> - <span class="codeline">$ cd ~/Hello-World<span>Changes the active directory in the prompt to your newly created folder</span></span> + <span class="codeline">$ mkdir ~/Hello-World<span>Creates a directory for your project called "Hello-World" in your user directory</span></span> + <span class="codeline">$ cd ~/Hello-World<span>Changes the current working directory to your newly created directory</span></span> <span class="codeline">$ git init<span>Sets up the necessary Git files</span></span> - <span class="terminal-output">Initialized empty Git repository in /Users/<em>your_user_directory</em>/Hello-World/.git/</span> - <span class="codeline">$ touch README<span>Creates a file called "README" in your Hello-World folder</span></span> + <span class="bash-output">Initialized empty Git repository in /Users/<em>your_user_directory</em>/Hello-World/.git/</span> + <span class="codeline">$ touch README<span>Creates a file called "README" in your Hello-World directory</span></span> </pre> - Open the new README file found in your Hello-World folder in a text editor and add the text “Hello World!.” When you are finished, save and close the file. + Open the new README file found in your Hello-World directory in a text editor and add the text “Hello World!.” When you are finished, save and close the file. 2. <span class="step-title">Commit your README</span> diff --git a/_posts/2011-02-17-fork-a-repo.markdown b/_posts/2011-02-17-fork-a-repo.markdown index 29fd3e4..0ae782d 100644 --- a/_posts/2011-02-17-fork-a-repo.markdown +++ b/_posts/2011-02-17-fork-a-repo.markdown @@ -27,7 +27,7 @@ You’ve successfully forked the Spoon-Knife repo, but so far it only exists Run the following code: <pre class="terminal bootcamp"> - <span class="codeline">$ git clone git@github.com:<em>username</em>/Spoon-Knife.git<span>Clones your copy of the repo into the current folder in terminal</span></span> + <span class="codeline">$ git clone git@github.com:<em>username</em>/Spoon-Knife.git<span>Clones your copy of the repo into the current directory in terminal</span></span> </pre> 2. <span class="step-title">Configure remotes</span> @@ -42,7 +42,7 @@ You’ve successfully forked the Spoon-Knife repo, but so far it only exists ##<span>Then:</span> More Things You Can Do -Congratulations, you’ve successfully forked a repo, but get a load of these other cool things you can do: +You’ve successfully forked a repo, but get a load of these other cool things you can do: - <span class="step-title">Push commits</span> @@ -89,24 +89,37 @@ Congratulations, you’ve successfully forked a repo, but get a load of thes <div class="more-info"> <h4 class="compressed">How do I use branches?</h4> <div class="more-content"> - + <p> Branches are pretty easy to work with and will save you a lot of headaches, especially when working with multiple people. To create a branch and begin working in it, use the following script: </p> <pre class="terminal bootcamp"> - <span class="codeline">$ git branch newbranch<span>Creates a new branch called "newbranch"</span></span> - <span class="codeline">$ git checkout newbranch<span>Makes "newbranch" the active branch</span></span> + <span class="codeline">$ git branch <em>mybranch</em><span>Creates a new branch called "mybranch"</span></span> + <span class="codeline">$ git checkout <em>mybranch</em><span>Makes "mybranch" the active branch</span></span> </pre> <p>Alternatively, you can use the shortcut:</p> <pre class="terminal bootcamp"> - <span class="codeline">$ git checkout -b newbranch<span>Creates a new branch called "newbranch"</span></span> + <span class="codeline">$ git checkout -b <em>mybranch</em><span>Creates a new branch called "mybranch" and makes it the active branch</span></span> </pre> <p>To switch between branches, use <code>checkout</code>.</p> + <pre class="terminal bootcamp"> + <span class="codeline">$ git checkout master<span>Makes "master" the active branch</span></span> + <span class="codeline">$ git checkout <em>mybranch</em><span>Makes "mybranch" the active branch</span></span> + </pre> + + <p>Once you’re finished working on your branch and are ready to combine it back into the <code>master</code> branch, use <code>merge</code>.</p> + + <pre class="terminal bootcamp"> + <span class="codeline">$ git checkout master<span>Makes "master" the active branch</span></span> + <span class="codeline">$ git merge <em>mybranch</em><span>Merges the commits from "mybranch" into "master"</span></span> + <span class="codeline">$ git branch -d <em>mybranch</em><span>Deletes the "mybranch" branch</span></span> + </pre> + </div> </div> diff --git a/_posts/2011-02-18-be-social.markdown b/_posts/2011-02-18-be-social.markdown index 67935fa..f83cbc7 100644 --- a/_posts/2011-02-18-be-social.markdown +++ b/_posts/2011-02-18-be-social.markdown @@ -60,6 +60,18 @@ At some point you may want to stay up-to-date with a specific project. We’ Congratulations! You are now watching the the Hello World project. If the Octocat updates it, you will see what happened in your dashboard. +##<span>Then:</span> More Things You Can Do + +You’ve done some of the most basic social interaction GitHub has to offer, but don’t stop there! Check out these other social features: + +- <span class="step-title">Pull requests</span> + + If you are hoping to contribute back to the original fork, you can send the original author a [pull request](/pull-requests/). + +- <span class="step-title">Issues</span> + + When you are collaborating on a project with someone, you some times come across problems that need to be fixed. To help you keep track of these problems, each GitHub repo has a section called Issues. For an example, check out the [issues](https://github.com/octocat/Spoon-Knife/issues) for the Spoon-Knife repo. + ##<span>Lastly:</span> Celebrate Congratulations! You are quite the socialite. What do you want to do next? diff --git a/css/style.css b/css/style.css index 5d7bd66..75100a1 100755 --- a/css/style.css +++ b/css/style.css @@ -131,6 +131,7 @@ pre .codeline:hover span { pre.bootcamp { white-space: normal !important; margin-left: -10px !important; + margin-bottom: 1.5em !important; background-image: none !important; } @@ -216,90 +217,6 @@ pre .codeline:hover em { } /****************************/ -/* Explain Pop-up */ -/****************************/ -/* -.explain { - font-style: italic; - color: #4183C4; - cursor: default; - margin: 1em 0px 1em; - position: relative; - display: inline-block; -} - -.explain-it-shell { - display: none; - position: absolute; - width: 667px; - padding: 15px 0 0 0; - top: 2.2em; - font-style: normal; - color: #666666; - margin: -15px 0 0 0; -} - -.explain:hover .explain-it-shell { - display: block; - z-index: 100; -} - -.explain-it-shell span.explain-it { - -webkit-border-radius: 3px; - -moz-border-radius: 3px; - border-radius: 3px; - background-color: #FFFFFF; - border: 3px solid #DDDDDD; - padding: 1em 2em; - display: block; - -webkit-box-shadow: 1px 1px 3px rgba(0, 0, 0, 0.3); - -moz-box-shadow: 1px 1px 3px rgba(0, 0, 0, 0.3); - box-shadow: 1px 1px 3px rgba(0, 0, 0, 0.3); -} - -.explain-it-shell span.explain-it img { - border: 1px solid #DDDDDD; - margin: 0; - -webkit-box-shadow: none; - -moz-box-shadow: none; - box-shadow: none; -} - - -.explain .triangle { - display: block; - width:31px; - height:15px; - position: absolute; - top: 3px; - left: 15px; - background-image: url('/images/bootcamp/explain_it_triangle.png'); - background-repeat: no-repeat; - background-position: right 50%; -} - -.explain .account-settings { - left: 70px; -} -.explain .ssh-public-keys { - left: 215px; -} -.explain .add-another-public-key { - left: 400px; -} -.explain .account-admin { - left: 220px; -} - -.explain h4 { - margin-top: 1em; -} - -.explain pre { - margin-left: 0px; -} -*/ -/****************************/ /* Bootcamp */ /****************************/ .short-bottom-marg { @@ -404,13 +321,15 @@ h2 span { .more-info { margin: 10px 0; + position: relative; } .more-info > h4 { background-image: url('/images/bootcamp/dropdown_sprites.jpg'); background-repeat: no-repeat; - padding: .25em 0 .25em 33px; + padding: .25em 0 .25em 25px; cursor: pointer; color: #4183C4; + font-weight: normal; } .more-info h4.compressed { background-position: 0 0; @@ -445,4 +364,5 @@ h2 span { .more-info .more-content pre { margin-left: 0px !important; -}
\ No newline at end of file +} + |