Module 03 of 10

Secure Version Control

Lessons

About This Module

Your repository is where all of your work lives, which makes it one of the first things an attacker wants to reach and one of the easiest places to make a costly mistake. Secure version control means using Git in a way that keeps your history trustworthy, your important branches safe, and your credentials out of the codebase.

You'll start with how Git works: commits, branches, and merges. From there the module covers branch protection rules, which stop risky changes such as direct pushes and force pushes from reaching your main branch, and can require reviews, passing checks, and signed commits before anything is merged. You'll finish with secret scanning and push protection, which catch API keys and passwords before they are pushed. Once a secret has been committed it stays in your history even after you delete it, so stopping it early matters.

With a protected repository in place, you'll be ready for the next module, CI/CD Pipelines, where you automate building, testing, and deploying your code.

Lessons

4 videos
01

Git Explained in 100 Seconds

A quick introduction to Git: initializing a repository, staging files, committing snapshots, and branching off and merging back.

02

How Git Works Explained

A clear walkthrough of what happens when you clone, stage, commit, push, pull, and branch, and how those pieces fit into a collaborative workflow.

03

GitHub Branch Rules: Protect Your Git Branches

How branch protection rules let you control who can delete or force push to important branches, and set requirements that changes must meet before they merge.

04

GitHub: Enabling Secret Scanning Push Protection

How to turn on push protection in GitHub so pushes that contain secrets are blocked before those credentials reach your repository.