Your First Git Commit, Explained

Git is a tool that takes snapshots of your project. Every snapshot is called a commit. If you break something, you can jump back to any old snapshot. This is also why AI coding is safer than it sounds — if the AI wrecks your code, git lets you rewind.

The three-command loop

1. 1git status — what has changed since the last snapshot
2. 2git add <files> — mark which changes go into the next snapshot
3. 3git commit -m "message" — take the snapshot with a label

Your first real commit

# Step 1: tell git who you are (one-time setup) git config --global user.name "Your Name" git config --global user.email "you@example.com" # Step 2: start a repo in your project folder cd my-project git init # Step 3: write some code in a file, then: git status # see what changed git add hello.py # stage the file git commit -m "first commit" # take the snapshot # Step 4: check it worked git log # shows your commit history

Why commit often

• Before accepting a big AI change, commit what you have — easy rollback
• After each working feature, commit — your history reads like a story
• Small commits are easier to review and revert than giant ones
• A green test + a commit is a natural save point

Undoing things

Push to GitHub

Once you commit locally, you can push your code to GitHub so it lives on the internet and can be shared. Create a repo on github.com, then run the two git remote commands GitHub shows you. You now have a portfolio link you can send anywhere.

“Version control is the single most important tool in software engineering. AI did not change that.”

The big idea: git gives you a safety net that makes experimenting with AI code fearless. Commit early, commit often, and you can always return to a working state.