Skip to content
>devspeak
← glossary
level 3Git & Version Control

Commit

also: commits, committed, committing, commit message

A saved snapshot of your project's changes in Git, with a short note describing what changed. You can come back to it later.

a bit more technical

An entry in a repository's history containing a snapshot of the tracked files, a message, an author, a timestamp, and a link to the previous commit. Each commit has a unique ID called a hash. As a verb: to record staged changes as a new commit.

picture it

A save point in a video game with a label, like "before the dragon." You keep playing, and you can always return to exactly that moment.

why it matters

Commits are your checkpoints. Committing before and after each agent task means any bad change can be undone cleanly, one step at a time.

what your agent might say
agent
Committed as 3f9a2c1: 'Add CSV export to admin dashboard.' 4 files changed. I haven't pushed yet.
how you might use it
you → your agent
Commit the current working state with a clear message before you start. Then make a separate commit for each step, so I can undo any one of them.
common mistake

Thinking a commit is backed up online. A commit lives only on your computer until you push it to a remote.

builds on