Committing code in Git is a fundamental part of version control. It allows you to save snapshots of your project, track changes over time, and collaborate with others more effectively.
In this guide, we’ll cover everything you need to know about making commits in Git—from staging changes to writing clear commit messages.
✅ What is a Git Commit?
A commit in Git is like a save point in a game. It records the current state of your files, including what changed and when. Each commit has a unique ID and message describing what was changed.
🔹 Step 1: Make Changes to Your Project
Before you can commit, you need to modify or create files in your Git-tracked repository.
Example:
echo "Hello, Git!" > hello.txt
🔹 Step 2: Stage Your Changes
You must add files to the staging area before committing:
git add hello.txt
To stage all changes (new, modified, deleted):
git add .
Or for modified files only:
git add -u
🔹 Step 3: Commit Your Changes
Once your changes are staged, commit them with a message:
git commit -m "Add hello.txt with greeting"
💡 Tips for Good Commit Messages:
- Use the imperative mood (e.g., “Add feature” not “Added feature”)
- Be concise but descriptive
- Capitalize the first letter
- Avoid generic messages like “update” or “stuff”
🔹 Optional: Check Status and Log
View staged and unstaged changes:
git status
View your commit history:
git log
🔹 Optional: Amend the Last Commit
If you forgot to include something or want to edit your message:
git commit --amend
🧠 Summary
Task | Command |
---|---|
Stage changes | git add <filename> or git add . |
Commit with message | git commit -m "Your message" |
Check status | git status |
View history | git log |
Amend last commit | git commit --amend |
🚀 Final Thoughts
Committing code is an essential skill for any developer using Git. It’s more than just saving your work—it’s about creating a meaningful project history that you and your team can rely on.
With good commit habits, you’ll:
- Collaborate more smoothly
- Debug more effectively
- Understand your code’s evolution