Git Notes

Hub Benefits of Git and GitHub - Why They Matter Git vs GitHub Version Control System What Is Git What Is GitHub Configure Git - User Identity and Settings Create GitHub Account - Sign Up Guide First Git Repository - Getting Started Install Git on Linux - Complete Setup Guide Install Git on macOS - Installation Guide Install Git on Windows - Step-by-Step Guide Git Add - Stage Changes Git Clone - Copy Remote Repositories Locally Git Commit - Save Changes Git Diff - Compare Changes in Your Repository Git Ignore - Exclude Files from Version Control Git Init - Initialize Repository Git Log - View Commit History Git Status - Check Repository State Git Fetch - Download Remote Changes Without Merging Git Pull - Fetch and Merge Remote Changes Git Push - Upload Local Commits to Remote Repository Git Remote - Manage Remote Repository Connections Local Repository - Understanding Your Git Working Environment Remote Repository - Collaborate Through Shared Repositories Sync Local and Remote - Keep Repositories in Harmony Amend Commit - Fix Last Commit Delete Branch - Clean Up Branches Git Reset - Move HEAD and Undo Commits Git Restore - Discard Changes Git Revert - Safely Undo Changes Recover Lost Commits - Reflog Guide Fork Repository GitHub Pages GitHub Profile Setup GitHub Repositories GitHub Stars and Watchers Repository Settings Code Reviews Git Clone Git Fetch Git Pull Git Push GitHub Issues Labels and Milestones Open Source Contributions GitHub Project Boards Pull Requests - Propose and Review Code Changes Team Collaboration with Git and GitHub Automated Testing with GitHub Actions CI/CD with GitHub Actions Deployment Automation with GitHub Actions Introduction to GitHub Actions GitHub Actions Runners GitHub Actions Workflows Enterprise Git Workflows - Scale Git for Large Organizations Feature Branch Workflow - Isolate Development Work GitFlow Workflow - Structured Release Management Monorepo Workflow - Manage Multiple Projects in One Repository Trunk-Based Development - Ship Code Fast and Safely Deployment Workflows GitHub Pages Deployment Netlify Deployment from GitHub Render Deployment from GitHub Vercel Deployment from GitHub Branch Protection Rules - Secure Your Git Branches Personal Access Tokens - Authenticate with GitHub Repository Security Best Practices Secret Scanning - Detect Leaked Credentials in Code Signed Commits - Verify Commit Authenticity with GPG SSH Keys - Secure Git Authentication Without Passwords Git Bisect - Find Bugs with Binary Search Git Cherry-Pick - Apply Specific Commits to Any Branch Git Hooks - Automate Workflows with Git Events Git Internals - Understanding How Git Works Under the Hood Git Stash - Temporarily Save Uncommitted Changes Git Submodules - Manage External Dependencies as Git Repos Git Tag - Mark Important Points in History Git Worktrees - Work on Multiple Branches Simultaneously Collaborative Web App Project Complete Team Workflow Project GitHub Actions Project - Build a CI/CD Pipeline Open Source Project Contribution - Guided Exercise Portfolio Project with Git - Showcase Your Skills Git Command Cheatsheet Git Interview Questions - Comprehensive Preparation Guide GitHub Interview Questions Scenario-Based Git Interview Questions Git Troubleshooting Guide Git Best Practices - Professional Development Habits Common Git Errors and Fixes - Quick Solutions Git Command Reference - Complete Command Guide Learning Resources - Continue Your Git & GitHub Education Branch Strategies - Choosing the Right Git Branching Model Create Branch in Git - Start New Development Lines Fast-Forward Merge in Git - Clean Linear History Git Branch Git Checkout Git Merge Git Rebase Merge Branches in Git - Combine Development Work Merge Conflicts - Resolve Git Conflicts Like a Pro Switch Branch in Git - Navigate Between Branches

Git Status - Check Repository State

Learn git status command to monitor repository state, track changes, understand file statuses, and keep track of uncommitted work for effective version control.

git status shows the state of your working directory and staging area. Use it constantly to understand what changed and what will be committed.

Basic Usage

bash example

git status

# Output:
# On branch main
# Changes to be committed:
#   new file:   README.md
#
# Changes not staged for commit:
#   modified:   index.html
#
# Untracked files:
#   .DS_Store
#   config.env

Understanding Output

On branch main ├─ You're on the main branch Changes to be committed: ├─ Staged changes (will be in next commit) ├─ green text Changes not staged for commit: ├─ Unstaged changes (need git add) ├─ red text Untracked files: ├─ New files not tracked ├─ Not in .gitignore

File Status Categories

Example

M = Modified (changed) A = Added (new file staged) D = Deleted (file removed) R = Renamed C = Copied U = Updated but unmerged ?? = Untracked

Short Status Format

bash example

git status -s
# or
git status --short

# Output:
# M  index.html        (modified, not staged)
# A  README.md         (added, staged)
# D  old-file.js       (deleted, staged)
# ?? config.env        (untracked)

Detailed Example

bash example

git status

# On branch main
# Your branch is ahead of 'origin/main' by 2 commits.
#
# Changes to be committed:
#   new file:   app.js
#   modified:   package.json
#
# Changes not staged for commit:
#   modified:   config.js
#
# Untracked files:
#   .env
#   build/

Workflow with Status

Example

1. Make changes $ git status # modified: file.js 2. Stage changes $ git add file.js $ git status # Changes to be committed: file.js 3. Commit $ git commit -m "message" $ git status # nothing to commit, working tree clean 4. Push $ git push origin main $ git status # Your branch is up to date with 'origin/main'

Common Scenarios

Working tree clean:

bash example

$ git status
# On branch main
# nothing to commit, working tree clean
# ✓ All changes committed

Untracked files:

bash example

$ git status
# Untracked files:
#   node_modules/
#   .env
# Add to .gitignore to hide

Ahead of remote:

bash example

$ git status
# Your branch is ahead of 'origin/main' by 3 commits
# Use: git push

Behind remote:

bash example

$ git status
# Your branch is behind 'origin/main' by 5 commits
# Use: git pull

Tips

Run frequently to stay aware
Before committing: verify status
Before pushing: check status
Untracked files won't be committed
Red = not committed, Green = will be committed

Interview Q&A

Q1: What information does git status provide?

A: Current branch name, staged changes (ready to commit), unstaged changes (need git add), untracked files, and relationship to remote (ahead/behind). Tells you exactly what's different from last commit and what will be included in next commit.

Q2: Difference between staged and unstaged changes?

A: Staged changes (green text) are marked for next commit via git add. Unstaged changes (red text) are modified but not staged. Only staged changes go into commits. Use git diff to see unstaged, git diff --staged to see staged.

Q3: What does "working tree clean" mean?

A: All changes have been committed. No untracked files, no modified files. Repository matches last commit exactly. You're caught up with local work.

Q4: What should you do with untracked files shown in status?

A: Either: (1) Stage and commit if they should be tracked, or (2) Add to .gitignore if they shouldn't be tracked (build files, env files, etc). Without action, they'll keep appearing in status output.

Q5: How often should you use git status?

A: Constantly! Beginner habit: run after each change. Professional habit: automatic from editor integrations. Status is free, safe, and informative. Before committing, before pushing, when confused—always run status first.

Advanced Git Status Scenarios

Understanding git status output in complex situations helps you navigate real-world workflows confidently.

Merge Conflicts: During a merge conflict, git status shows files marked as "both modified" under an "Unmerged paths" section. These files need manual conflict resolution before you can continue the merge. After resolving conflicts, git add the file to mark it as resolved.

bash example

$ git status
On branch main
You have unmerged paths.
  (fix conflicts and run "git commit")

Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   src/utils.js

Interactive Rebase: During an interactive rebase, status shows which step you're on and what state the rebase is in:

bash example

$ git status
interactive rebase in progress; onto abc1234
Last command done (1 command done):
   pick def5678 Add login feature
Next command to do (2 remaining commands):
   pick ghi9012 Fix validation bug

Detached HEAD: When you checkout a specific commit (not a branch), status warns you about the detached HEAD state:

bash example

$ git status
HEAD detached at abc1234
nothing to commit, working tree clean

Integrating Git Status Into Your Workflow

Editor Integration: Modern editors (VS Code, IntelliJ, Vim with fugitive) show git status inline — modified files appear with indicators in the file explorer, and changed lines are highlighted in the gutter. This gives you real-time awareness without switching to the terminal.

Shell Prompt: Configure your shell prompt to display the current branch and dirty state. Tools like oh-my-zsh, starship, or bash-git-prompt show branch name, ahead/behind counts, and dirty indicators directly in your terminal prompt. This means you always know your repository state at a glance.

Pre-commit Hooks: Use git status in pre-commit hooks to verify that only intended files are being committed. This prevents accidentally committing temporary files, environment configs, or sensitive data.

Aliases for Common Patterns: Many developers create shorter aliases for status variants they use frequently:

bash example

git config --global alias.st status
git config --global alias.ss "status -s"

Exam Focus

Revise definitions, diagrams, examples, and short-answer points for Git Status - Check Repository State.

Interview Use

Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.

Search Terms

git-github, git & github, git, github, basics, status, git status - check repository state

Related Git & GitHub Topics

Continue learning this concept

Git BasicsGit Add - Stage ChangesMaster the git add command for staging changes, understanding the staging area, staging specific files, patterns, and preparing commits for version control.Git BasicsGit Clone - Copy Remote Repositories LocallyLearn how to use git clone to copy remote repositories to your local machine. Understand clone options, shallow clones, and best practices for cloning repositories.Git BasicsGit Commit - Save ChangesComplete guide to git commit command including commit messages, best practices, amending commits, commit history, and working with atomic commits for clean Git history.Git BasicsGit Diff - Compare Changes in Your RepositoryMaster the git diff command to compare changes between commits, branches, and staging areas. Learn diff output format, comparison options, and practical examples.Git BasicsGit Ignore - Exclude Files from Version ControlLearn how to use .gitignore files to exclude files and directories from Git tracking. Master patterns, global ignores, and best practices for different project types.Git BasicsGit Init - Initialize RepositoryLearn git init command to create new repositories, understand .git directory structure, initialize existing projects, and set up repository configuration for version control.

PreviousGit Log - View Commit History NextGit Fetch - Download Remote Changes Without Merging

Git Notes

Git Status - Check Repository State

Learn git status command to monitor repository state, track changes, understand file statuses, and keep track of uncommitted work for effective version control.

git status shows the state of your working directory and staging area. Use it constantly to understand what changed and what will be committed.

Basic Usage

bash example

git status

# Output:
# On branch main
# Changes to be committed:
#   new file:   README.md
#
# Changes not staged for commit:
#   modified:   index.html
#
# Untracked files:
#   .DS_Store
#   config.env

Understanding Output

File Status Categories

Example

M = Modified (changed) A = Added (new file staged) D = Deleted (file removed) R = Renamed C = Copied U = Updated but unmerged ?? = Untracked

Short Status Format

bash example

git status -s
# or
git status --short

# Output:
# M  index.html        (modified, not staged)
# A  README.md         (added, staged)
# D  old-file.js       (deleted, staged)
# ?? config.env        (untracked)

Detailed Example

bash example

git status

# On branch main
# Your branch is ahead of 'origin/main' by 2 commits.
#
# Changes to be committed:
#   new file:   app.js
#   modified:   package.json
#
# Changes not staged for commit:
#   modified:   config.js
#
# Untracked files:
#   .env
#   build/

Workflow with Status

Example

Common Scenarios

Working tree clean:

bash example

$ git status
# On branch main
# nothing to commit, working tree clean
# ✓ All changes committed

Untracked files:

bash example

$ git status
# Untracked files:
#   node_modules/
#   .env
# Add to .gitignore to hide

Ahead of remote:

bash example

$ git status
# Your branch is ahead of 'origin/main' by 3 commits
# Use: git push

Behind remote:

bash example

$ git status
# Your branch is behind 'origin/main' by 5 commits
# Use: git pull

Tips

Run frequently to stay aware
Before committing: verify status
Before pushing: check status
Untracked files won't be committed
Red = not committed, Green = will be committed

Interview Q&A

Q1: What information does git status provide?

Q2: Difference between staged and unstaged changes?

Q3: What does "working tree clean" mean?

A: All changes have been committed. No untracked files, no modified files. Repository matches last commit exactly. You're caught up with local work.

Q4: What should you do with untracked files shown in status?

Q5: How often should you use git status?

Advanced Git Status Scenarios

Understanding git status output in complex situations helps you navigate real-world workflows confidently.

bash example

$ git status
On branch main
You have unmerged paths.
  (fix conflicts and run "git commit")

Unmerged paths:
  (use "git add <file>..." to mark resolution)
        both modified:   src/utils.js

Interactive Rebase: During an interactive rebase, status shows which step you're on and what state the rebase is in:

bash example

$ git status
interactive rebase in progress; onto abc1234
Last command done (1 command done):
   pick def5678 Add login feature
Next command to do (2 remaining commands):
   pick ghi9012 Fix validation bug

Detached HEAD: When you checkout a specific commit (not a branch), status warns you about the detached HEAD state:

bash example

$ git status
HEAD detached at abc1234
nothing to commit, working tree clean

Integrating Git Status Into Your Workflow

Aliases for Common Patterns: Many developers create shorter aliases for status variants they use frequently:

bash example

git config --global alias.st status
git config --global alias.ss "status -s"

Exam Focus

Revise definitions, diagrams, examples, and short-answer points for Git Status - Check Repository State.

Interview Use

Prepare one clear explanation, one practical example, and one common mistake for this Git & GitHub topic.

Search Terms

git-github, git & github, git, github, basics, status, git status - check repository state

Related Git & GitHub Topics

Continue learning this concept

PreviousGit Log - View Commit History NextGit Fetch - Download Remote Changes Without Merging