0.5 Git, enough for infrastructure work
You can version infrastructure code and recover from a mistake.
Before:nothing requiredUnlocks:01. Cloud Foundations
Infrastructure in this course lives in Git, so the basics arrive early: commits, branches, pull requests, and the habit of never committing a credential. The habit that matters most is treating an infrastructure change like a code change — reviewed, versioned, revertable. The confusion worth clearing now is what Git is for here: not backup, but a record of what changed, when, and by whom, which is what you will want at three in the morning when something broke at two.
Work through these
init, add, commit, log, diff
The core loop of version control: start a repository, stage what changed, record it, then read the history and the differences. Everything else in this unit is built on these five operations.
Branches, merges and pull requests
Working on a copy of the history and merging it back is how more than one person changes infrastructure without overwriting each other. Branches, merges and pull requests are the names for that arrangement, and reviews happen at the last of them.
Never committing credentials; .gitignore and secret scanning
A credential committed once is in the history forever, even after you delete the line. This item is about the ignore file and the scanning that keep it from getting in, because removal after the fact is the hard path.
Why infrastructure lives in Git at all
Putting infrastructure in version control gives you review, history and the ability to recreate an environment from scratch. It is the practice the whole later unit on infrastructure as code depends on.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.