The core idea
Git is a distributed version control system. It records changes to files so developers can review history, experiment in branches, and collaborate without relying on a single shared working copy.
How it works
A repository contains project files and their version history. Start tracking a folder with git init, or copy an existing remote repository with git clone.
Practical considerations
The basic workflow is to edit files, inspect changes with git status and git diff, stage selected changes with git add, and create a commit with git commit. A commit records a snapshot and a message describing the change.
A useful way to apply it
Branches let developers work on changes independently. Create a branch for a feature or fix, commit work there, and merge it after review and testing.
Keep learning
Before pushing code to a shared remote, check what will be included. Avoid committing passwords, API keys, generated secrets, or large temporary files. Use a .gitignore file for files that should not be tracked.
Frequently asked questions
What is a Git commit?
A commit is a recorded snapshot of staged changes, accompanied by metadata and a message.
What is the difference between Git and GitHub?
Git is version control software. GitHub is a hosting and collaboration platform for Git repositories.
Should every small change have a commit?
Commits should represent understandable units of work. Small, focused commits are often easier to review.
Continue learning
Explore more topics in the MicroProgrammer library, or browse the Developer Tools collection for related guides.