Compiled Learning Objectives

GitHub.dev

• Access the dotdev environment on a library computer if you do not have your own

Install VSCode

• Download and install VSCode
• Identify the key parts of the VSCode interface

Create a work folder

• Navigate and manipulate the file system using a terminal
• Create a named directory to store your work over the course

Version control software

• Define a repository
• Define a commit
• Explain the purpose of version control software

Sharing history

• Identify the number of commits on the main branch of a remote repository
• Identify the author, time and message of a given commit on GitHub

Inspecting a commit

• Given a remote repository on GitHub, identify the files and folders from any commit in a version timeline

Inspecting previous versions

• Use a Git history to view previous versions of a project
• Find the commit that corresponds to a particular version of a project

Forking a repository

• Create a fork of a repository

Working locally

• Clone a remote repository from GitHub into a local folder
• Define the terms ‘remote’ and ’local’ in the context of GitHub

Viewing files from a git clone

• Open a cloned repository in your IDE
• Explore the repository in your IDE
• Open the Integrated Terminal in VSCode

Branching

• Explain why a git repository may have multiple branches
• Describe what’s special about the branch named main
• Create a new local branch in a git repository

Wrapping up Git

• Commit changes to a local git branch

00 Read and watch How This Works

• Explain the importance of prep
• Subscribe to the global calendar
• Locate the quickstart curriculum overview

🗺️ Using the curriculum

• Describe our mission
• Identify the key elements of our educational philosophy
• Describe how a flipped classroom works
• Identify the key pages of the curriculum interface
• Explain the sequencing of work in a typical week

Workshop: Using GitHub

• Make sense of an issue, pull request, and file tree view.
• Identify the purpose of a repo by reading its README file.
• Predict and discover hidden information available in the GitHub interface

Sharing Our Blockers

• Identify blockers
• Share blockers on a board or sticky notes

Study Group Development

• Create a strategy for implementing a program based on a set of requirements.
• Express questions, problems and blockers as formal bug reports
• Interpret business requirements and express them as test cases.
• Open a pull request and iterate on it in response to feedback.