The short version
Git is a version control system. It tracks changes to files over time. Every developer uses it, and three operations cover most of daily work: commit, push, and pull request. Each one builds on the previous.
How it works
Commit
A commit is a saved checkpoint. It records exactly what changed, when, and who made the change. Every commit has a message describing what was done:
git commit -m "Fix broken login button on mobile"
Commits are local. They only exist on your computer until you share them. You can make as many as you like before sharing. Think of them as save points in a game.
Push
A push sends your commits to a remote server (usually GitHub). This is how you share your work with the team:
git push
Once pushed, others can see your changes, and your work is backed up. If your laptop dies, the code survives.
Pull request (PR)
A pull request is a proposal. You're saying: "I've made these changes. Please review them before they go into the main codebase."
PRs aren't a Git feature. They're a GitHub (and GitLab, Bitbucket) feature built on top of Git. They add:
- A description of what changed and why
- A diff showing every line added, removed, or modified
- A review process where teammates can comment, approve, or request changes
- Automated checks (tests, linting) that run before merging
The flow: commit → push → open PR → get reviewed → merge.
Why it matters
These three operations are the rhythm of modern software development. Even if you never write code, understanding them helps you follow technical conversations, read changelogs, and understand how software gets built.