# You're mid-feature with unsaved work
git status
# modified: src/feature.js
# modified: src/styles.css
 
# Stash everything (staged + unstaged)
git stash
# Saved working directory and index state WIP on main: ...
 
# With a descriptive name (recommended for multiple stashes)
git stash push -m "WIP: adding notification system"
 
# Your working directory is clean — now fix the urgent bug
git checkout -b hotfix/login-crash
# ... fix, commit, merge ...
 
# Return to your feature and restore stashed changes
git checkout feature/notifications
git stash pop  # apply the most recent stash AND remove it from stack
# Or apply without removing from stack (reusable):
git stash apply
 
# See all stashed work
git stash list
# stash@{0}: On feature/notifications: WIP: adding notification system
# stash@{1}: On main: WIP: started dashboard redesign
 
# Apply a specific stash
git stash pop stash@{1}
 
# Delete a stash without applying it
git stash drop stash@{0}
 
# Stash including untracked (new) files
git stash push -u -m "Include new files too"new files too"

# Create a lightweight tag at current commit
git tag v1.0.0
 
# Create an annotated tag with a message (preferred for releases)
git tag -a v1.0.0 -m "First stable release — adds user auth and dashboard"
 
# Tag a specific past commit by hash
git tag -a v0.9.0 9f3a2c1 -m "Beta release"
 
# See all tags
git tag
# v0.9.0
# v1.0.0
 
# See details of an annotated tag
git show v1.0.0
 
# Push tags to GitHub (not pushed by default!)
git push origin v1.0.0        # push one tag
git push origin --tags        # push ALL tags
 
# Delete a local tag
git tag -d v0.9.0
# Delete a remote tag
git push origin :refs/tags/v0.9.0

# A bug exists in the current HEAD but worked at some point
# Use bisect to find the exact culprit commit
 
# Start bisect
git bisect start
 
# Mark the current commit as 'bad' (has the bug)
git bisect bad
 
# Mark a known good commit (e.g., last week's release tag)
git bisect good v1.2.0
 
# Git checks out a commit in the middle
# TEST the bug:
# - If bug exists: git bisect bad
# - If bug doesn't exist: git bisect good
git bisect bad
# Git checks out another midpoint...
git bisect good
# After ~6-7 steps Git reports:
# 'a1b2c3d is the first bad commit'
# commit a1b2c3d Author: Dev <dev@co.com>
# Date: Mon Jan 6 ...
# Refactor user session handling
 
# Now you know which commit caused the bug!
 
# End bisect session (returns to original HEAD)
git bisect reset

# Search commit messages for a keyword
git log --grep="payment" --oneline
 
# Find which commits added or removed a specific string in code
git log -S "getUserById" --oneline
# This is the 'pickaxe' search — incredibly useful for tracking down when a function appeared
 
# See who last edited each line of a file (blame)
git blame src/auth.js
# Shows: hash | author | date | line content
 
# Blame a specific line range
git blame -L 20,40 src/auth.js
 
# Search all commits that changed a specific file
git log --follow --oneline src/auth.js
 
# Find deleted files
git log --all --full-history -- "**/deletedFile.js"