Version control is the practice of tracking changes to files over time so that you can see what changed, who changed it, and why — and roll back when something breaks. Git is the tool that does this tracking on your own machine; GitHub is the hosted platform that stores Git repositories online and adds collaboration features such as issues, pull requests, code review, and project boards. For the rest of this course, GitHub is where your team's prototype code, design assets, and documentation will live.
This topic matters because your course project is a team effort. Without a shared workflow, teammates overwrite each other's work, lose files, and lose track of who is responsible for what. A clean repository, a sensible branching strategy, and a habit of reviewing changes through pull requests will save your team far more time than it costs to set up in Module 1.
As you watch, keep three questions in mind. First, what is happening locally (on your computer) versus remotely (on GitHub)? Second, what is the minimum set of commands you actually need day to day — clone, add, commit, push, pull, branch, merge? Third, how does a pull request function as both a technical merge and a human conversation about the work? Try to follow along in a scratch repository rather than just watching passively.
This video draws the distinction between Git, the distributed version control system, and GitHub, the cloud platform built around it. Based on the title and description, it covers repositories, how changes are tracked, and how GitHub layers collaboration features such as issue tracking and integrations on top of Git. Expect a whiteboard-style conceptual overview rather than a hands-on terminal demo.
It directly addresses the "What Is Version Control?" and "GitHub as a Collaboration Platform" subtopics, and clearing up the Git-versus-GitHub confusion early prevents a lot of later frustration. IBM Technology's explainer format is clear and vendor-neutral enough for an introductory course.
A beginner-oriented walkthrough of the Git commands you will use most often, with worked examples. The description indicates it starts with configuring your Git setup and moves through the core workflow, so expect coverage of initializing or cloning a repository, staging and committing changes, and syncing with a remote. Branching is typically part of this essential command set as well.
Produced by GitHub itself, so the commands and terminology match what you will see in the platform's own documentation. It supports the "Creating and Configuring a Repository" and "Branching" subtopics with the practical, typo-level detail you need to actually get your team repository running.
A short, focused tutorial that walks through opening a pull request from start to finish. It demonstrates proposing changes to a repository and routing them to others for review before they are merged. At under four minutes, it is a procedural demo rather than a deep discussion of review etiquette.
Pull requests are the heart of collaborative work on GitHub, and this video covers the exact mechanics your team will repeat all semester. Its brevity makes it easy to rewatch while you are actually submitting your first pull request.
These videos primarily serve MO3: before a team can execute a project plan, it needs a shared place to store work and an agreed way of dividing and merging it. Setting up a repository, assigning branch and review responsibilities, and using issues or project boards turns an abstract plan of scope, platform, and team roles into something visible and trackable. The conceptual Git-versus-GitHub explainer also supports the broader Module 1 goal of building shared vocabulary, so that when you move on to usability, user experience, and accessibility work (MO1 and MO2), your team can document and version design artifacts and findings alongside code rather than scattering them across personal drives.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.