Real programmers commit constantly: after every small finished step, not once at the end of the day. Small commits are like frequent game saves: when something breaks, you only lose a few minutes of work.
Notice that after each commit you have new changes again (you kept working!), so the add → commit rhythm starts over. Watch the chain of circles grow downward as you go.
Two habits make your history great from day one. First: one idea per commit; if you fixed a bug AND added music, that's two commits. Second: many teams start each message with the kind of change it is, like "feat: add background music", "fix: stop the crash on level 2" or "refactor: tidy the score code". Git doesn't enforce this style (it's a convention called Conventional Commits), but it makes a log read like a story.
git add .Stage the new changes.git commit -m "feat: ..."Save the next snapshot; feat, fix and refactor are the classic message prefixes.Get into the rhythm: add, commit, repeat.
Open this level in your browser to type the commands at a live git prompt with an animated commit graph.