The Four Questions You Currently Ask Someone Else

What Git Actually Solves

Git Versus GitHub

What This Course Covers

A Repository Is a Folder With a Memory

Commits: Save Points That Never Get Overwritten

Branches: Working on a Copy

Merging, and What a Conflict Really Is

Exercise 1: Learn Your Team's Layout

The Repo Homepage

The README

Reading Activity

Finding the File You Want

Exercise 2: Read Your Own Repository

How Teams Organise Branches

'Done' and 'On Main' Are Different Claims

Long-Lived Branches Hurt

The Four States Work Can Be In

Exercise 3: Map Your Team's Flow

What a Pull Request Is

Reading a PR Without Reading Code

Checks, Reviews and Being Blocked

Commenting Usefully as a Non-Engineer

Exercise 4: Read Three Pull Requests

Red, Green and the Numbers

Judging Scope in Thirty Seconds

Three Things a PM Should Always Look For

When Small Diffs Are Big Changes

Exercise 5: Read Real Diffs

How Issues Differ From Your Tracker

Writing an Issue Engineers Can Act On

Labels, Milestones and Projects

Keeping the Trail Intact

Exercise 6: Write and File a Real Issue

Merged, Deployed, Released

Reading a Release

Version Numbers and What They Promise

Answering 'Is It Live?' Yourself

Exercise 7: Answer Your Own Release Questions

What a PM Can Safely Change

Editing a File in the Browser

Writing a PR Description That Helps

What Happens Next

Exercise 8: Open Your First Pull Request

Five Things to Never Do

Why Rewriting History Upsets People

Secrets Are Hard to Remove

When to Ask Instead

Exercise 9: Establish Your Boundaries

Trace a Real Change End to End

Part 1 — Map Your Team's Setup

Part 2 — Follow One Feature All the Way

Part 3 — Ship Something Yourself

Getting Oriented

Reading Changes

Filing and Tracking Work

Making Changes

Words Explained