Week 7: Git Basics

Week	Topic	Learning Objectives	Key Resources
7	Git Basics	Students will be able to explain what a repository is and how commits record the change history of document(s); create a new GitHub repository, clone it locally, and push to it to create a pull request successfully.	Week 7 Slides

Overview

• Text editors
• Code editors
  • VS Code Tutorial for Students
• Command line basics
  • Open the terminal
  • Use the command line to navigate directories and display directory contents.
  • Use the command line to create a new directory and a new file.
  • Use the command line to rename or destroy a directory and a file.
  • Use the command line to open a file or folder in a program.
• Command line advanced
  • Copy/paste commands
  • Tab completion
  • Open VS Code from the command line
• Git intro
  • Explain what Git and GitHub are and the differences between the two.
  • Describe the differences between Git and a text editor in terms of what they save and their record keeping.
  • Describe why Git is useful for an individual developer and a team of developers.
• Setting up Git
  • Install
  • Configure Git and GitHub
• Git Practice
  • Create a repository on GitHub
  • Move files into GitHub
  • Git best practices

Guidance for Mentors

Students tend to have trouble with Git and GitHub – consider using a whole mentor session practicing the Git workflow with students. Expect to have to practice it again in coming weeks!

Assignment Rubric

Check to ensure the following from your students:

• The student has downloaded and install VS Code and familiarized themself with its tools.
• The student has successfully created a new repository in their GitHub account. The repository has a proper name and description, is set to public, and has been initialized with a README file.
• The student has successfuly cloned the repository to their local machine. The student should use the HTTPS option and copy the correct repository address.
• The student has added their full name to the README.md file and has created a new index.html file in the project directory.
• The student has properly staged their changes, committed the staged changes with a descriptive commit message, and pushed the changes to their GitHub repository. The changes are visible in the lesson-7 branch of the repository.
• The student has followed the instructions to create a pull request for the lesson-7 branch on GitHub.