Working with Git involves a core set of commands for tracking changes, committing, viewing history, and synchronizing with remotes. Knowing them is fundamental, everyday practical knowledge.
git init # create a new repository in the current directory
git clone <url> # copy a remote repository locally
git config --global user.name "Name"
git config --global user.email
git status # what's changed, staged, untracked (use this CONSTANTLY)
git add <file> # stage a specific file
git add . # stage all changes
git commit -m "message" # record staged changes as a commit
git commit -am "message" # stage tracked files AND commit (shortcut)
git status is the most-used command — it shows the current state. add stages changes; commit records them as a snapshot with a message.
git log # commit history
git log --oneline --graph # compact history with branch graph
git diff # unstaged changes (working dir vs staged)
git diff --staged # staged changes (vs the last commit)
git show <commit> # details of a specific commit
git push # upload your commits to the remote
git pull # fetch + merge others' changes
git fetch # download remote changes WITHOUT merging
git remote -v # list configured remotes
Knowing the essential Git commands is fundamental, everyday practical knowledge for every developer, because Git is used constantly in software development and these commands are the daily mechanics of tracking and sharing work.
The core workflow commands — git status (the most-used command, showing what's changed, staged, and untracked, used constantly to understand the current state), git add (staging changes), and git commit (recording staged changes as a snapshot with a descriptive message) — are the fundamental cycle of saving work in Git, performed many times daily.
Understanding viewing history and changes (git log for commit history, git diff for seeing changes, git show for commit details) is essential for understanding what has changed and reviewing work — knowing the state of the code and its evolution.
The synchronizing commands (git push to share commits, git pull to get others' changes, git fetch to download without merging) are how collaboration happens, essential for team work.
Knowing the setup commands (init/clone, config) gets you started.
Since Git is integral to virtually all software development and these commands are the constant, daily mechanics of using it (saving work, viewing history, collaborating), knowing the essential Git commands is fundamental, frequently-applied knowledge — basic, must-have competency for any developer, the practical foundation of working with version control that's used countless times throughout every working day, and a baseline skill expected universally in software roles.
A library of IT interview questions with detailed answers — from Junior to Senior.
Donate