With a backend language picked, the next thing every project needs is a way to track changes and work with other people without overwriting each other's code. That's version control — and in practice, that means Git.
This module covers what version control actually solves, then walks through Git itself: commits, branches, and merges. From there it moves to GitHub, the most common place to host a Git repository, including how pull requests turn Git into a tool for code review and collaboration, not just backup. You'll also look at common branching strategies teams use to avoid stepping on each other's work, and how GitLab and Bitbucket compare to GitHub as alternatives.
By the end, you should be comfortable committing, branching, and pushing code to a remote repository — the foundation everything else in this course builds on top of, starting with Relational Databases.
The problem version control solves — tracking changes, working with a team, and never losing work — before diving into Git specifically.
The core Git workflow: initializing a repo, staging files, committing snapshots, and branching off into an alternate version of your code.
A full walkthrough of Git commands and GitHub itself — repos, remotes, cloning, and pushing your code up so others (and future you) can find it.
How to open a pull request on GitHub, why teams use them for code review, and what happens when one gets merged.
A tour of the most common branching workflows — feature branches, Git Flow, GitHub Flow, and trunk-based development — and when to use each.
How the three major Git hosting platforms compare, and what might push you toward one over the others for a given project or team.