convert from gitLab to GitHub

Author: libjohn

_handson_old.Rmd

@@ -0,0 +1,144 @@
+---
+title: "Git Workshop - Hands-On"
+output: html_document
+---
+
+```{r, message=FALSE, warning=FALSE, include=FALSE}
+library(tidyverse)
+library(DT)
+```
+
+```{r loaddata, message=FALSE, warning=FALSE, include=FALSE}
+hubs <- read_csv("data/hubs.csv")
+```
+
+### Generate SSH Keys 
+
+This must be done on each workstation you use to *push*.  
+
+- https://gitlab.oit.duke.edu/help/ssh/README
+
+This step was covered in the [Outline Section](outline.html#generate_ssh_keys_in_advance_of_the_workshop)
+
+## Make a Repository
+1. Duke's GitLab -- <a href="https://gitlab.oit.duke.edu" target="_blank">https://gitlab.oit.duke.edu</a>
+1. Duke Shibboleth Login
+1. New Project <br><figure>![](images/new_gitlab_project_button.png)</figure><br>
+1. Add a project name.  Use the name *test-one*  <br> <figure>![](images/project_name.png)<figcaption>replace 'my-awesome-project' with 'test-one'</figcaption></figure><br>
+
+1. Create Project<br><figure>![](images/create_project.png)</figure><br>
+
+    - GitLab will present a new page.  Notice the section below the *Command line instructions* header.  That information can come in handy.  For future repositories, you may want to make a note of those Git commands.  We will not use those commands today so you can move on. <br>&nbsp;
+
+1. Make a README file <br><figure>![](images/readme.png)
+<figcaption>Open in a new tab for each link: README, LICENSE, and .gitignore</figcaption></figure><br>
+
+    1. Make a top level heading with the word "README"
+    
+        - i.e. type:  `# README` 
+        - See [Markdown](markdown.html) for more information on Markdown tagging
+    1. After a blank line type: `This is my first GitLab repository.`
+    1. Commit changes  
+    
+    &nbsp; 
+    
+    
+1. Make a license file (Open in a New Tab, click the LICENSE link) <br><figure>![](images/license.png) 
+<figcaption>Appply a license format</figcaption></figure><br>
+
+    - choose *MIT* license, or paste a [Creative Commons](https://creativecommons.org/share-your-work/) License into license.md
+    - Commit changes
+    
+    &nbsp; 
+    
+1. Make a .gitignore file (Open in a New Tab, click the .gitignore link)
+
+    1. *Apply a .gitignore format* 
+    
+        - choose *R* 
+        
+    1. Commit changes
+    
+1. Congratulations.  You've just created your first GitLab repository.  Click *test-one* in the top-left of your GitLab repo screen.  Now you'll see your repository -- including the three files you just created.
+
+&nbsp; 
+
+## Clone
+
+**Using RStudio**, clone your repository.  Cloning will pull down the whole repo to your local system -- including the three files you just created.
+    
+### Bring the repo down locally via RStudio
+
+1. Copy GitLab repo URL to clipboard 
+
+	  - The repo should be at a location like this. `https://gitlab.oit.duke.edu/<<your-NetID>>/test-one`, copy the *git* URL to the clipboard by clicking the icon <br><figure>![](images/copy_repo.png)
+<figcaption>Copy the repo URL</figcaption></figure><br>
+	    
+1. Launch RStudio and create a *New Project...*
+
+    1. From the RStudio menubar:  *File > New Project...* > Version Control > Git <br><figure>![](images/project_version_git.png)<figcaption>Paste the GitLab repo URL (from the step above) into the  *Repository URL:* field in RStudio</figcaption></figure><br>
+    1. Create Project
+    1. You may be prompted with a message which asks if you about the "authenticity of host".  I like to verify the IP number is correct; then the answer is `yes`.<br><figure>![](images/yes.png)</figure><br>
+
+&nbsp; 
+
+## Push: Edit and Commit
+
+**Continue in RStudio**.  This time you'll make local changes by editing your local repository.  After saving the changes you'll *add* and *commit* the changes.  Lastly, you will *push* your changes up to the remote repository.
+
+<br><figure>![](images/push.png)</figure>
+
+### Edit
+
+1. In the Files Pane, Open the README.md file
+1. In the Editor Pane, modify your README with [Markdown](markdown.html)
+
+    - Make a Sub-heading with the word "Purpose"
+    
+        - i.e. `## Purpose`
+        
+    - After a blank line type: `This is my first Git repository.  I'm going to push this file to GitLab via RStudio.  Hello World.`
+1. Save the changes to this file
+
+
+### Commit & Push
+
+1. In the Git pane:
+
+    1. Check each of the staged files
+    1. Click *commit* and provide a message:  `this is my first edit of a README and supporting files`
+    1. Click the *commit* button to engage your commit  process with the message, then close
+    1. Click the *Push* arrow, then close, then close the commit dialogue box  
+<br><figure>![](images/commit_push.png)</figure><br>
+
+1. View your changes back at GitLab:  `https://gitlab.oit.duke.edu/<<your-NetID>>/test-one`
+
+&nbsp; 
+
+## Pull
+
+The next time you open your project in RStudio the first step you should take is to *Pull* from the GitLab repo.  Then make your changes, then commit and push.  If you forget to *Pull* you may have to resolve some conflicts. For best results, get into the habit of pulling before you make edits.
+
+<br><figure>![](images/git_push_pull.png)</figure>
+
+## Public or Private Repositories
+
+- `https://gitlab.oit.duke.edu/<<your-NetID>>/test-one` > Settings > Scroll to *Project Visibility* > right-hand drop-down list:  Private | Public
+- Add a Description (Optional)
+- Add Tags (Optional)  
+
+&nbsp; 
+
+## Public Hubs v Duke's Hub
+
+```{r, echo=FALSE, message=FALSE, warning=FALSE}
+datatable(hubs, rownames = FALSE, options = list(dom = 't'),
+          escape = FALSE) %>% 
+  formatStyle("Duke's GitLab", color = "silver", backgroundColor = "navy", fontWeight = "bold") %>% 
+  formatStyle("Public Hubs", backgroundColor = "lightblue")
+```
+
+
+&nbsp; 
+
+&nbsp;

_outline_old.Rmd

@@ -0,0 +1,101 @@
+---
+title: "Git & R/RStudio Prerequisites:  Software Installation"
+output: html_document
+---
+
+## Hands-on Outline
+
+1. Git
+1. GitHub and GitLab and Bitbucket
+
+    - Duke's GitLab  
+    
+1. Markdown  
+1. Orchestrating with RStudio
+
+	- Masks the CLI
+	- Easier to get started
+	- Power Users can still use commands
+	
+## Prerequisites
+
+### Load & Install Software **Before the Workshop**
+
+To complete the hands-on portion of the workshop you'll need software pre-installed.  Due to the nature of the workshop we will not have time to troubleshoot installations during the workshop.  Please be sure to perform the following steps **on the laptop you bring to the workshop**.  
+
+### Required Software
+
+#### Download and install  
+
+I recommend accepting the install defaults for the following:
+
+- **Git**: <a href="https://git-scm.com/downloads" target="_blank">https://git-scm.com/downloads</a>
+
+    1. Download and install Git
+    1. Run the install and accept all the defaults
+    
+<br><figure>![](images/git_os.png)<figcaption>Click on the link to your OS</figcaption></figure><br>
+    
+- **R**: <a href="http://archive.linux.duke.edu/cran/"" target="_blank">http://archive.linux.duke.edu/cran/</a>
+
+    - If you have not installed R before choose *install R for the first time*
+    - If you already have R installed on your workstation I recommend running the latest version, but any reasonably current version should be fine.
+    
+- **RStudio**: <a href="https://www.rstudio.com/products/rstudio/download/#download" target="_blank">https://www.rstudio.com/products/rstudio/download/#download</a> 
+
+<br><figure>![](images/rstudio_download.png)</figure><br>
+    
+
+If you haven't yet, install each of the above applications.  
+
+
+### **Duke's** GitLab -- Verify *your NetID* Access
+
+During the workshop we will use <a href="https://gitlab.oit.duke.edu" target="_blank">Duke's GitLab</a>.  To complete the hands-on portion of the workshop, you **must log-in** -- **in advance** of the workshop -- and ensure you have NetID access to <a href="https://gitlab.oit.duke.edu" target="_blank"> https://gitlab.oit.duke.edu</a>.  If you do not have access to **Duke's** GitLab, [contact OIT](https://oit.duke.edu/help).
+
+- Be certain you log-in via "Duke Shibboleth Login" using your NetID
+
+<br><figure>![](images/gitlab_shib_login.png)</figure><br> 
+
+### Generate SSH keys in Advance of the Workshop
+
+I recommend generating your SSH keys in advance of the workshop.  Then add your public key to Duke's GitLab.  To do so, you should have already installed Git to your laptop.  
+
+We will cover key configuration in the workshop although you will find the explanation easier to follow if you generate and add your keys in advance.  The instructions below are based on those found at Duke's GitLab.  If the instructions below are not clear you should consult the more complete [GitLab instructions](https://gitlab.oit.duke.edu/help/ssh/README)  
+
+1. To begin, open the **Terminal** *in RStudio*.  If you're using the latest version of RStudio, the *Terminal* is a tab in the console quadrant (typically the bottom-left)
+
+    - In RStudio: Menubar `Tools > Terminal > New Terminal` 
+
+<br><figure>![](images/shell.png)</figure><br>
+
+    
+2. Determine if you already have an SSH key pair.  In the *Termnal* tab, type:  `cat ~/.ssh/id_rsa.pub`
+    
+    - If you see a string starting with `ssh-rsa` you already have an SSH key pair and can simply copy that key (Step 5)
+        
+    - If you get some kind of error, you'll have to generate a key in the next step (Step 3)
+        
+1. In the *Terminal* tab, type:  `ssh-keygen -t rsa -C "[email protected]" -b 4096`
+
+    - Use your Duke Email address  
+    
+1. You will be prompted to input a file path.  i.e. the location where you'll save your SSH key pair.
+
+    - If you don't already have an SSH key pair use the suggested path by pressing enter
+    
+     - After setting the file path you will be prompted to input a password.  This will secure your SSH key pair. It is a best practice to use a password for an SSH key pair, but it is not required.  You can skip creating a password by pressing enter
+
+        - **Note**:  If you want to change the password of your SSH key pair, you can use `ssh-keygen -p <keyname>`  
+    
+1. Copy the public SSH key to the clipboard buffer
+
+    - In the *Termnal* tab, type the appropriate code below:
+        - **macOS**:  `cat ~/.ssh/id_rsa.pub | pbcopy`
+        - **Windows**:  `cat ~/.ssh/id_rsa.pub | clip`
+    
+1. The final step is to add your public SSH key to GitLab.
+
+    - Navigate to the *SSH Keys* tab in your *Profile Settings.* Paste your key in the *Key* section and give it a relevant *Title*. Use an identifiable title like *Work Laptop - Windows 7* or *Home MacBook Pro 15.*
+    
+    - If you manually copied your public SSH key make sure you copied the entire key starting with `ssh-rsa` and ending with your email.

docs/README.html

@@ -81,6 +81,9 @@
 .tabbed-pane {
   padding-top: 12px;
 }
+.html-widget {
+  margin-bottom: 20px;
+}
 button.code-folding-btn:focus {
   outline: none;
 }