Initial commit

.github/ISSUE_TEMPLATE/suggestion.md

@@ -0,0 +1,16 @@
+---
+name: Suggestion
+about: Suggest an improvement for this training
+title: '[SUGGESTION] Suggestion title'
+labels: 'suggestion'
+
+---
+
+**What module is your suggestion regarding?**
+_Ex 1.2_
+
+**What is your suggestion for improving this module?**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the suggestion here.

AWS Cloud9/README.md

@@ -0,0 +1,18 @@
+# Module 5 - Utilizing AWS Cloud9 in the Classroom
+In this lesson we are going to take an opportunity to explore AWS Educate and AWS Cloud9.  Becoming an AWS Educate member provides a wide variety of benefits. The one benefit we will explore in this lesson is the ability to use the AWS Cloud9 IDE for free. Cloud9 is a cloud-based IDE, a place where you can write, run, and debug your code with just a browser.
+
+In this module you will signup for a free AWS Educate Account and explore how to provide your students access. Afterwards, we will dive into how to use GitHub Classroom alongside AWS Educate to expose your students to the industry tool, AWS Cloud9 IDE.
+
+5.1 Join AWS Educate
+
+:tv: [Getting Started with AWS Educate](https://s3.amazonaws.com/awseducate-onboarding/Educator+Toolkit/Movies/Getting+Started+with+AWS+Educate.mp4)
+
+:notebook:[Create an AWS Educate account](https://aws.amazon.com/education/awseducate/)
+
+5.2 Create an AWS Classroom
+
+:tv: [Getting Started with AWS Educate Classrooms](https://s3.amazonaws.com/awseducate-onboarding/Educator+Toolkit/Movies/AWS+Educate+Educator+Classrooms+Overview.mp4)
+
+5.3 The Student Perspective: Assigning an AWS Cloud9 Assignment
+
+:tv: [The Student Perspective: Assigning an AWS Cloud9 Assignment](https://youtu.be/bBPRD8ytWcI)

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2019 Campus Advisors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

Module 0/Module 0.1 Assignment.md

@@ -0,0 +1,28 @@
+# Assignment 0.1: Getting Started
+
+1. Register for an account on [github.com](https://github.com/).
+2. [Download](https://git-scm.com/downloads), install, and [configure](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup) git. Windows users please install [Git for Windows](https://gitforwindows.org/).
+3. If you are new to Git, GitHub, and the command-line, we recommend[downloading ATOM](https://atom.io/), a text editor, which is available for Mac, Linux, and Windows. ATOM will be used in all modules.
+
+    #### Mac and Linux Setup
+      If you are using a Mac or Linux machine, I would recommend following these instructions to setup the ATOM command-line:
+      - [ATOM command-line Instructions](https://youtu.be/h5xcw8_8gaE)
+
+    #### Chromebook User Setup
+      If you are using a Chromebook, great news! You can use ATOM to follow along with the videos with some easy instructions:
+      - [Instructions and setup for ATOM for Chromebook Users](https://blog.atom.io/2018/10/02/running-atom-on-chome-os.html)
+      - [ATOM command-line Instructions](https://youtu.be/h5xcw8_8gaE)
+
+    #### Windows User Setup
+      If you are using Windows, and new to the command-line, I would recommend following additional instructions to avoid using the default shell, known as "PowerShell," in ATOM since all of the examples in the modules will be using a Unix based shell:
+      - [Instructions and setup for using ATOM in Windows](https://youtu.be/0aVAjhVZ9Ko)
+
+4. Make sure to set Git with your name and email address using the following commands on the command-line with your name and email address:
+```
+$ git config --global user.name "FirstName LastName"
+$ git config --global user.email "[email protected]"
+```
+Git will use this information when you work on a project.
+
+## Submission
+There is no submission for this assignment

Module 0/Module 0.2 Assignment.md

@@ -0,0 +1,9 @@
+# Assignment 2: Teacher Toolbox
+In order to fully take advantage of GitHub Education teacher benefits, you’ll need the Teacher Toolbox (if you do not already have it).
+
+Head over to the [Teacher Toolbox](https://education.github.com/toolbox) and fill out the application. You’ll need to provide dated proof that you are a faculty member at your institution, so have that on hand.
+
+Some Teacher Toolbox applications require a manual review and may take longer to receive a decision and response. After you have applied, your confirmation page will indicate approximately how long your application review may take.
+
+## Submission
+There is no submission for this assignment

Module 0/README.md

@@ -0,0 +1,12 @@
+# Module 0
+
+Welcome to Module 0!
+
+In this module we’ll get you set up with everything you need to complete the GitHub Education Teacher Training.
+
+## Lessons
+All assignment files can be found at the top of this page.
+
+-  📺 [Module 0.0 Video](https://youtu.be/Ub8IMMMTfB8)
+-  📓 Complete Module 0.1 Assignment
+-  📓 Complete Module 0.2 Assignment

Module 1/Module 1.1 Assignment.md

@@ -0,0 +1,22 @@
+# Module 1.1 Assignment
+
+For a majority of your assignments you will create issues on GitHub.
+
+In order to create an issue you will travel to the tab marked as `Issues` (**here is an example screenshot of the original repository; you will create your issues in your own repository**):
+
+![](https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module%201/assets/issue_one.png)
+
+Once you click on that tab you will see all the current issues in this repository. At this point, no issues have been created. Let's create a new issue by clicking `New issue`
+
+![](https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module%201/assets/issue_two.png)
+
+Once you have created a new issue, you will be greeted by the screen below. Here you will provide
+* A title for your issue (Every title should be the name of the assignment, so in this case it is "Module 1.1 Assignment")
+* A body for your issue to write a response or upload a screenshot
+* A submission button
+
+![](https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module%201/assets/issue_three.png)
+
+For the Module 1.1 Assignment, copy the question below and paste it into the body of the issue, then answer it:
+
+`Given what you have learned about Git, why would you want to use Git in your classroom?`

Module 1/Module 1.2 Assignment.md

@@ -0,0 +1,17 @@
+For the Module 1.2 Assignment, you will open up your command line and complete the following:
+
+- [ ] Create a directory using the command `mkdir`
+- [ ] In the directory you created initialize Git using `git init`
+- [ ] Create a README.md file in your directory using the `touch` command
+- [ ] Make sure README.md is in your _Working Directory_ by checking your status with `git status`
+- [ ] Move README.md from the _Working Directory_ to the _Staging Area_ by using `git add`
+- [ ] Make sure README.md is in your _Staging Area_ by checking your status with `git status`
+- [ ] Commit README.md to your repository using `git commit`
+- [ ] Make sure your _Working Directory_ and _Staging Area_ are clean with `git status`
+- [ ] Make sure your commit has been logged into your repository by using `git log`
+
+Once you have completed these steps, take a screenshot of your command line, with the steps above, and upload your screenshot to a new `Issue` titled `Module 1.2 Assignment`. I have added the screenshot from the Module 1.1 Assignment for reference.
+
+![](https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module%201/assets/issue_three.png)
+
+In the body of the issue you can drag and drop your screenshot or search for it on your device. Once you have added the screenshot you can submit the issue and move to the next lesson.

Module 1/Module 1.3 Assignment.md

@@ -0,0 +1,14 @@
+# Module 1.3 Assignment
+
+Now that you have learned more about Git, on the command line I would like you to do the following:
+
+- [ ] Create a file called `teacher_training.txt` in the directory you created in Module 1.2
+- [ ] Write "Hello GitHub Education!" in `teacher_training.txt` and **commit** your changes
+- [ ] Now write "Hola GitHub Education!" in `teacher_training.txt`
+- [ ] Show the differences between your _Working Directory_ and _Staging Area_
+- [ ] Add `teacher_training.txt` to your _Staging Area_
+- [ ] Show the differences between your _Staging Area_ and your _Repository_
+- [ ] Commit teacher_training.txt to your repository
+
+Once you have completed these steps, take a screenshot of your command line, with the steps above, 
+and upload your screenshot to a new Issue titled Module 1.3 Assignment.

Module 1/Module 1.4 Assignment.md

@@ -0,0 +1,12 @@
+# Module 1.4 Assignment
+
+You were introduced to the tool [Visualizing Git](http://git-school.github.io/visualizing-git/) in this lesson. I would like you to replicate this visualization using Visulaizing Git:
+
+![A git visualization showing dots to represent commits. From left to right, there is a commit labeled "first commit", then another commit. From there the commits fork into two directions. There is a line continuing to extend straight to the right with 1 commit that has a branch label that says "new-feature". There is another diagonal line extending from the fork going up and to the right. The diagonal line has 1 commit highlighted in green that has a branch label, "master", as well as a label that says "HEAD".](https://github.com/github-campus-advisors/Campus-Advisor-Training/blob/master/Module%201/assets/visualize_git.png)
+
+Note, there is more than one way to replicate this visualization. 
+
+- [ ] Go to [Visualizing Git](http://git-school.github.io/visualizing-git/)
+- [ ] Replicate the image above by determining the correct sequence of git commands
+- [ ] Take a screenshot of your work, including the command line, in the visualizer
+- [ ] Upload your screenshot to a new Issue titled Module 1.4 Assignment

Module 1/README.md

@@ -0,0 +1,42 @@
+# Welcome to Module 1: Git Basics
+
+In this module you will be introduced to Git. This module will cover:
+
+* What is version control?
+* What is Distributed Version Control?
+* What is a Git repository?
+* Basic Bash and Git commands
+* The Git workflow and the Three State Model
+* How to be selective with Git commits
+* How does Git save commits
+* How to branch and merge your branches
+
+## Lessons
+
+**All assignment files can be found at the top of the page.**
+
+### Module 1.1: Meet Git
+
+[:tv: Module 1.1 Video](https://youtu.be/uWsXEmaM3PA)
+
+:notebook: Complete Module 1.1 Assignment
+
+### Module 1.2: The Three State Model
+
+[:tv: Module 1.2 Video](https://youtu.be/yLLZdOIuCfg)
+
+:notebook: Complete Module 1.2 Assignment
+
+### Module 1.3: Being Selective with Git
+
+[:tv: Module 1.3 Video](https://youtu.be/3zmolo8YRO8)
+
+:notebook: Complete Module 1.3 Assignment
+
+### Module 1.4: Branches and Merging
+
+[:tv: Module 1.4 Video](https://youtu.be/2YDoQZ9nZ4g)
+
+:notebook: Complete Module 1.4 Assignment
+
+

Module 2/Module 2.1 Assignment.md

@@ -0,0 +1,19 @@
+# Module 2.1 Assignment
+
+In this lesson, you learned how to create a remote repository from scratch. But what happens if you want to create a local version of a remote repository that already exists? Now, if a repository already exists, and it already has code that you want, you can actually copy it to your local machine using the command `git clone` followed by the Repository URL.  
+
+In this assignment, you’ll learn how to clone a repository on GitHub to your local machine, allowing you to manage and edit files locally. To complete this assignment, follow the instructions below:
+
+1. Navigate to the main page of this repository on GitHub. Click the green button that says `Code` then copy the URL by clicking the gray clipboard icon. (**here is an example screenshot of the original repository; you will clone your own repository**)
+
+     ![GIF demonstrating how to copy a remote URL](https://user-images.githubusercontent.com/2359538/107465091-36aaec80-6b27-11eb-8c04-fcc055dbaa0d.png)
+
+2. On the command line, type `git clone` along with the URL you copied earlier, then press Enter.  
+```
+$ git clone https://github.com/YOUR-REPOSITORY.git
+```
+
+3. After the repository has successfully cloned to your machine, type `ls` in your terminal to view the newly cloned repository in your machine’s directory.
+
+## Submission
+To submit this assignment, create an issue titled `Module 2.1 Assignment` in this repository. In the issue, provide a screenshot of your command line showing the commands you used to complete this assignment, then proceed to the next section in this module.

Module 2/Module 2.2 Assignment.md

@@ -0,0 +1,12 @@
+# Module 2.2 Assignment
+
+In this lesson, you learned how to commit file changes, create branches, and fetch and pull updates from GitHub. To complete this assignment, you’ll change this file in a new branch on GitHub and then pull the changes to your local repository by following the instructions below:
+
+1. Create a new branch named `edit-module-assignment` on GitHub
+2. On the `edit-module-assignment` branch, edit this file `Module 2.2 Assignment.md` by clicking the pencil, or 'Edit', icon
+3. In the editor for `Module 2.2 Assignment`, add your name on the first line above the title, then scroll towards the bottom of the page and click “Commit changes”
+4. On the `Campus-Advisor-Training` repository you cloned to your computer in the last assignment, fetch and merge the changes you’ve made in this file into your `master` branch using the command line
+
+
+## Submission
+To submit this assignment, create an issue titled `Module 2.2 Assignment` in this repository. In the issue, provide a screenshot of your command line showing the commands you used to complete this assignment, then proceed to the next section in this module.

Module 2/Module 2.3 Assignment.md

@@ -0,0 +1,12 @@
+# Module 2.3 Assignment
+
+In this lesson, you learned more about how branches are used in the GitHub workflow. To complete this assignment, you’ll use the command line to create a new branch and change this file in your local repository by following the instructions below:
+
+1. Create a new branch named `assignment-edit` in your local repository using the command line
+2. Edit this file `Module 2.3 Assignment.md` by using a text editor to add your name on the first line above the title, then save your changes
+3. Push your changes to GitHub from the command line (Need help pushing to GitHub? [Watch Module 2.1](https://youtu.be/R2bLo-KiYlU))
+4. Create a Pull Request on GitHub after you’ve pushed your changes to compare the two branches, then merge these changes into the `master` branch
+5. Delete the `assignment-edit` branch after you’ve successfully merged your branch
+
+## Submission
+To submit this assignment, create an issue titled `Module 2.3 Assignment` in this repository. In the issue, provide a screenshot of your command line showing the commands you used to complete this assignment, then proceed to the next section in this module.

Module 2/Module 2.4 Assignment.md

@@ -0,0 +1,27 @@
+# Module 2.4 Assignment
+
+In this lesson, you learned about merge conflicts. To complete this assignment, you’ll create a `README.md` file that says “Hello World”. Copy and paste the following commands on your command line, then press Enter:
+
+```
+mkdir MergeConflict
+cd MergeConflict/
+git init
+touch README.md
+echo "echo Hello" > README.md
+git add .
+git commit -m "first commit on master"
+git checkout -b new-branch
+echo "Hello World" > README.md
+git add .
+git commit -m "first commit on new-branch"
+git checkout master
+echo "Hola" > README.md
+git add .
+git commit -m "second commit on master"
+git merge new-branch
+```
+
+This "script" will create a merge conflict. Resolve the merge conflict so the text in `README.md` is `"Hello World"`.
+
+## Submission
+To submit this assignment, create an issue titled `Module 2.4 Assignment` in this repository. In the issue, provide a screenshot of your command line showing the commands you used to resolve the merge conflict in this assignment, then proceed to the next module.

Module 2/README.md

@@ -0,0 +1,38 @@
+# Welcome to Module 2: GitHub Basics
+
+In this module you will be introduced to GitHub. This module will cover:
+
+* Communicating with a remote
+* Git commands for working with a remote
+* Fetching and Pulling from GitHub
+* Git commands to request updates from GitHub
+* The GitHub Workflow
+* Resolving Merge Conflicts
+
+## Lessons
+
+**All assignment files can be found at the top of the page.**
+
+### Module 2.1: Pushing to a Remote
+
+[:tv: Module 2.1 Video](https://youtu.be/R2bLo-KiYlU)
+
+:notebook: Complete Module 2.1 Assignment
+
+### Module 2.2: Fetching and Pulling from a Remote
+
+[:tv: Module 2.2 Video](https://youtu.be/gNaCC_8B1k0)
+
+:notebook: Complete Module 2.2 Assignment
+
+### Module 2.3: GitHub Workflow
+
+[:tv: Module 2.3 Video](https://youtu.be/SoaAoATcUxU)
+
+:notebook: Complete Module 2.3 Assignment
+
+### Module 2.4: Merge Conflicts
+
+[:tv: Module 2.4 Video](https://youtu.be/c1210JclnPw)
+
+:notebook: Complete Module 2.4 Assignment

Module 3/Module 3.1 Assignment.md

@@ -0,0 +1,13 @@
+# Module 3.1 Assignment
+
+In this lesson, you learned how to create your own Classroom. To practice, rearrange the instructions below in the correct order to create your own Classroom. 
+1. Authorize access to GitHub Classroom for your GitHub account 
+2. Add a student roster
+3. Start at classroom.github.com and sign in with your GitHub account
+4. Click the “Create your first classroom” button, then create and/or authorize an organization for your new classroom
+5. Invite TAs and admins to your GitHub organization and send them your classroom invitation URL
+6. Name your classroom (e.g. Fall 2020 CS101), then click continue
+
+
+## Submission
+There is no submission for this assignment

Module 3/Module 3.2 Assignment.md

@@ -0,0 +1,25 @@
+# Module 3.2 Assignment
+
+In this section, you learned how to create your first assignment in GitHub Classroom by completing the following the instructions:
+- Navigate to the classroom you created in section 3.1, then click “Create your first assignment”
+- Fill out the assignment details
+  - Assignment title
+  - Assignment deadline
+  - Select type of assignment (individual or group)
+  - Select the repository visibility (public/private)
+  - Select whether you’d like your students to have admin access to their repositories
+- Provide starter code for the assignment by selecting an existing repository
+- Enable feedback pull requests on all student repositories
+- Click “Create assignment”  
+
+
+To practice, create an individual assignment in GitHub Classroom that contains the following:
+- No assignment deadline
+- Starter code from a repository in your organization (Need help creating a repository? Watch our [Git and GitHub Basics video](https://www.youtube.com/watch?v=tswF0wpAbTo))
+- Private repository visibility
+- Enabled feedback pull requests on all student repositories  
+
+
+## Submission
+There is no submission for this assignment
+