Version Control, 2005
Git makes sense once you can see what it actually stores. This era gives you a practice repository and walks the core loop: init, add, commit, branch, merge, and reading the history back with log.
Code and data track · 8 missions · boss mission, no written exam · free, no signup. Everything below runs in the browser terminal on the SERVBG home page.
What you will do
- create a new repository
git initLinus Torvalds wrote Git in ~10 days in 2005 after the BitKeeper fallout. The name is British slang for an unpleasant person — self-deprecating.
- see what has changed
git statusgit status is the command you run most — staged, unstaged, untracked. Your working reality at a glance.
- stage changes for the next commit
git add .The staging area (the "index") is Git's quiet superpower: you choose exactly what goes into each commit.
- record a snapshot
git commit -m "first commit"A commit is an immutable snapshot plus a hash. History is a chain of them — nothing committed is ever truly lost.
- create a line of development
git branch featureA branch is just a 40-byte pointer. That cheapness rewired how the entire world collaborates on code.
- move onto a branch
git switch -c featureSwitch branches to work in parallel without stepping on anyone. Merge them back when ready.
- combine two branches
git merge featureMerging weaves two histories into one. A conflict is just Git asking you to decide — not a failure.
- Boss missionread the project history
git loggit log is a time machine: every author, message and decision. The story of the code, kept forever.
Certificate
This is one of the original eras, so it ends at the boss mission: there is no written exam and no certificate for it. Clearing the boss marks the era complete and banks the XP. The expansion tracks (networking, Cisco IOS, FortiOS, containers, Kubernetes, cloud, operations, defence, models and the nine graphics eras) are the ones that carry exams.