Commit

A commit is one saved snapshot of your project's changes, paired with a short note describing what changed, giving you a labeled point in history you can return to later.

A commit is one saved snapshot of your project's changes, paired with a short note describing what changed, giving you a labeled point in history you can return to later. Each commit bundles a related set of edits and stamps them with a message, an author, and a time, so the history reads like a list of meaningful steps rather than one undifferentiated blob. Say your to-do app gains a working password reset. You ask your coding assistant to commit that work with the message "Add password reset flow." From then on, that exact version is a named point you can open, compare against, or restore if a later change breaks something.

Builder example

When an AI coding assistant edits your project, asking it to commit after each working step lets you review a long autonomous session one piece at a time. If the assistant builds a support bot's reply feature in one commit and a logging change in the next, you can inspect each step, keep the one that works, and undo the one that does not. A single giant commit at the end forces you to accept or reject everything together, so you cannot separate out the one bad change without discarding the good work bundled with it.

Common confusion: Saving a file writes the current text to disk and overwrites what was there. A commit records a snapshot into your project's tracked history with a message, so you can return to that exact state later. Saving keeps one current version; committing keeps a timeline of versions.