DorrisWord
Commit
A commit is one saved snapshot of your project's files, with a short note saying what changed and why.
Also called: checkpoint, revision
Think of it as a labeled save point. Each one records the exact state of every tracked file at that moment, so you can see what the project was before a change and return to it when the change turns out to be a mistake.
Commit when something works, not at the end of the day. Small snapshots with honest notes are what make a history worth reading.
What people get wrong: edits sitting on your screen, or saved to disk but not committed, are not in the history at all. Until you commit, git does not know it happened.