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.

Validator

⏱ 0:00

IDLE — checks run live as you type commands; submit when done

01Requirements

live checks

~/project is a Git repository○
A commit with message 'feat: add health endpoint' exists○
A commit with message 'fix: handle empty payload' exists○

02Walkthrough

13 steps

01
Create the project folder
Every lab starts from a fresh shell, so the folder does not exist yet.
mkdir ~/project
02
Enter the repository
Commits only exist inside a repository - move into the folder first.
cd ~/project
03
Initialize the repository
An empty repository has nothing to commit, so give it a file right after init.
git init
04
Create the first file
A README is enough - the point of this lab is the commit messages.
touch README.md
05
Stage and commit
Stage everything, then record a chore commit. chore marks housekeeping that changes nothing for users.
git add .
06
Commit the chore
The type prefix comes first, a colon and a space, then the description in lower case.
git commit -m "chore: init repository"
07
Add the feature
Create the file the feature will live in, stage it and commit it as a feature.
touch health.py
08
Stage and commit the feature
feat marks user-visible functionality - it is what release tooling turns into a version bump.
git add .
09
Commit the feature
Keep the description short and in the imperative mood.
git commit -m "feat: add health endpoint"
10
Add the fix
Create a second file and stage it the same way.
touch payload.py
11
Commit the fix
fix marks a correction to shipped behaviour - it goes into the patch notes, not the release headline.
git add .
12
Commit the fix
git log shows all three messages in one place.
git commit -m "fix: handle empty payload"
13
Verify and submit
Review the history, then submit for validation.
git log

03Stuck?

0 of 3 revealed

Take a hint without losing the lab — each one points at the thing to look at, not at the answer.

04AI Tutor

guides, never solves

Tell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?

04Notebook

saved locally in this browser

learner@lab — ubuntu:24.04 + git

Session is disposable

↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list

← Previous lab

Write a .gitignore That Actually Works

Git

Next lab →

Deploy the Application as a Container

Docker