Module · DevOps Engineer

Git

Version control as a way of working, not a memorized command list.

5 topics6 interactive tasks

Tool Deep-Dive Available

View full architecture diagrams, CLI cheatsheets, and production gotchas.

Open Git Hub ↗

TOPIC 01

Git Basics

Repositories, staging, commits and reading history.

What you'll practice

Your First Commit — guided · beginner

A command you'll meet

cd ~/project

Open any task below to get the full step-by-step walkthrough — every command is explained, and the lab validator checks what you actually built.

Hands-On Tasks in This Topic (1)

beginner

Guided Task

Your First Commit

Initialize a Git repository in ~/project, stage every file and create the initial commit with the message 'init'. Every command is explained in the walkthrough.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡

TOPIC 02

Branches & Merging

Isolate work, then bring it back together.

What you'll practice

Ship a Feature Branch — practice · beginner

A command you'll meet

cd ~/project

Open any task below to get the full step-by-step walkthrough — every command is explained, and the lab validator checks what you actually built.

Hands-On Tasks in This Topic (1)

beginner

Practice Task

Ship a Feature Branch

The daily Git loop: branch, commit on the branch, merge back to main. Create a branch called 'feature', commit on it and merge it into main.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡

TOPIC 03

Remotes & GitHub

Connect a local repository to the world.

What you'll practice

Connect to a Remote — guided · beginner

A command you'll meet

cd ~/project

Open any task below to get the full step-by-step walkthrough — every command is explained, and the lab validator checks what you actually built.

Hands-On Tasks in This Topic (1)

beginner

Guided Task

Connect to a Remote

Local commits are only half the story. Add GitHub as a remote and push your branch. In this lab the push is simulated — the workflow is identical to the real thing.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡

TOPIC 04

Fixing Mistakes

Reverting bad changes without rewriting history.

What you'll practice

Revert a Bad Commit — scenario · intermediate

A command you'll meet

cd ~/project

Open any task below to get the full step-by-step walkthrough — every command is explained, and the lab validator checks what you actually built.

Hands-On Tasks in This Topic (1)

intermediate

Scenario

Revert a Bad Commit

A teammate committed a bug and you need main clean again — without rewriting history that others already have. Undo the last commit with git revert, which adds an inverse commit.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡

TOPIC 05

Ignore Rules & Commit Discipline

Keep the wrong files out of the repository and make every commit message say something useful.

What you'll practice

Write a .gitignore That Actually Works — practice · intermediate
Use Conventional Commit Messages — guided · beginner

A command you'll meet

git add .

What you stage is what you ship. Open the task below for the full walkthrough.

Hands-On Tasks in This Topic (2)

intermediate

Practice Task

Write a .gitignore That Actually Works

A .gitignore is a list of patterns, not a list of files - one line can cover a thousand files. Create a repository with rules for environment files, logs and build output.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡

beginner

Guided Task

Use Conventional Commit Messages

Commit messages are read by humans and by release tooling. Learn the type prefix convention - feat for features, fix for bugs, chore for everything else.

Environment: ubuntu:24.04 + gitLaunch Lab ⚡