0
Total Commands
0
Visible
0
Categories
Filter by Category:
How to Use This Git Cheatsheet
Welcome to your ultimate Git command reference! This interactive tool helps you quickly find and learn Git commands with ease.
Search & Filter
- Search Bar: Type keywords like "commit", "branch", or "merge" to instantly find relevant commands
- Category Filters: Click category buttons to view specific command groups (Basic, Branching, Remote, etc.)
- Real-time Results: Commands filter instantly as you type or select categories
Understanding the Statistics
Total Commands: All Git commands available in the cheatsheet
Visible: Commands currently displayed based on your filters
Categories: Number of command categories available
Visible: Commands currently displayed based on your filters
Categories: Number of command categories available
The statistics update dynamically as you search and filter, helping you track how many commands match your criteria.
Copy Commands
- Individual Copy: Click "Copy" button on any command card to copy that specific command
- Copy All Visible: Use the "Copy All Visible" button to copy all commands currently shown
- Visual Feedback: Button turns green and shows "Copied!" when successful
Reset & Clear
Click the "Reset Filters" button to clear all search terms and category filters, returning to the complete command list.
About Git & This Tool
Git is a distributed version control system created by Linus Torvalds in 2005. It's the most widely used version control system in software development, powering millions of projects worldwide.
This Cheatsheet is designed to be your go-to reference for Git commands. Whether you're a beginner learning the basics or an experienced developer needing a quick reminder, this tool provides instant access to essential Git commands with clear descriptions.
Why Git?
- Distributed Architecture: Every developer has a complete copy of the repository
- Branching & Merging: Powerful branching model enables parallel development
- Speed & Performance: Optimized for fast operations, even with large projects
- Data Integrity: Cryptographic integrity of your codebase history
- Collaboration: Enables seamless teamwork across distributed teams
Interesting Git Facts
- Git was created in 2005 by Linus Torvalds to manage Linux kernel development
- The name "Git" is British slang for "unpleasant person" - Linus Torvalds named it jokingly
- Over 90% of developers use Git according to Stack Overflow surveys
- GitHub hosts over 200 million repositories making it the largest code host in the world
- Git is incredibly fast - most operations are performed locally without network latency
- Linux kernel repository has over 1 million commits and is managed entirely with Git
- Git uses SHA-1 hashes to ensure the integrity of your code history
- Everything is local - you can work offline and commit without internet connection
Additional Tips & Best Practices
Commit Message Best Practices
- Use imperative mood: "Add feature" not "Added feature"
- Keep first line under 50 characters: Think of it as an email subject
- Add detailed description: Explain what and why, not how
- Reference issues: Include ticket numbers like "Fixes #123"
git commit -m "Add user authentication module
Implements JWT-based authentication system with refresh tokens.
Includes login, logout, and session management.
Fixes #456"
Branching Strategy Tips
- Use descriptive branch names: feature/user-auth, bugfix/login-error, hotfix/security-patch
- Keep branches short-lived: Merge frequently to avoid conflicts
- Delete merged branches: Keep your repository clean
- Protect main branches: Use branch protection rules on production branches
Performance Tips
- Use .gitignore: Exclude unnecessary files from version control
- Shallow clone for large repos: Use --depth flag to limit history
- Git LFS for large files: Track binary files efficiently
- Prune regularly: Clean up old remote-tracking branches
Security Best Practices
- Never commit secrets: Use environment variables for API keys
- Review before pushing: Use git diff to check changes
- Sign commits: Use GPG keys to verify authorship
- Enable 2FA: Protect your Git hosting account
Common Use Cases
Starting a New Project
git init
git add .
git commit -m "Initial commit"
git remote add origin <repository-url>
git push -u origin main
Initialize a new repository, add all files, make your first commit, and push to a remote server.
Feature Development Workflow
git checkout -b feature/new-feature
# Make changes
git add .
git commit -m "Add new feature"
git push origin feature/new-feature
# Create pull request
# After approval
git checkout main
git pull origin main
git merge feature/new-feature
Create a feature branch, develop your feature, push it, and merge back to main after review.
Bug Fix Workflow
git checkout -b bugfix/fix-login-error
# Fix the bug
git add .
git commit -m "Fix login validation error"
git push origin bugfix/fix-login-error
Create a bugfix branch, fix the issue, and push for review.
Undoing Changes
# Undo uncommitted changes
git checkout -- <file>
# Undo last commit (keep changes)
git reset --soft HEAD~1
# Undo last commit (discard changes)
git reset --hard HEAD~1
# Revert a specific commit
git revert <commit-hash>
Different ways to undo changes depending on your situation.
Syncing with Remote
# Update your local repository
git fetch origin
git pull origin main
# Update and rebase your work
git pull --rebase origin main
# Push your changes
git push origin main
Keep your local repository in sync with the remote server.
Practical Examples
Example 1: Collaborative Development
Scenario: You're working on a team project and need to add a new feature while keeping up with other developers' changes.
# Clone the repository
git clone https://github.com/team/project.git
cd project
# Create your feature branch
git checkout -b feature/user-profile
# Make changes and commit
git add src/profile.js
git commit -m "Add user profile page"
# Before pushing, get latest changes
git checkout main
git pull origin main
# Merge main into your feature branch
git checkout feature/user-profile
git merge main
# Resolve conflicts if any, then push
git push origin feature/user-profile
Example 2: Emergency Hotfix
Scenario: Critical bug in production needs immediate fix.
# Create hotfix branch from main
git checkout main
git checkout -b hotfix/critical-security-bug
# Fix the bug
git add .
git commit -m "Fix security vulnerability in auth"
# Merge to main
git checkout main
git merge hotfix/critical-security-bug
# Deploy and tag
git tag -a v1.2.1 -m "Security hotfix"
git push origin main --tags
# Cleanup
git branch -d hotfix/critical-security-bug
Example 3: Reviewing History
Scenario: Need to find when a bug was introduced.
# View commit history
git log --oneline --graph --all
# Search commits by message
git log --grep="login"
# Find when file was changed
git log --follow src/auth.js
# See who changed what
git blame src/auth.js
# Use bisect to find bug
git bisect start
git bisect bad HEAD
git bisect good v1.2.0
# Git will checkout commits for testing
Example 4: Stashing Work
Scenario: Need to switch branches but have uncommitted work.
# Save current work
git stash save "Work in progress on feature X"
# Switch branches and do other work
git checkout main
# Do something else
# Return to your branch
git checkout feature/my-feature
# Restore your work
git stash pop
# Or list all stashes
git stash list
# Apply specific stash
git stash apply stash@{0}
Copied to clipboard!
| Feature | Details |
|---|---|
| Price | Free |
| Rendering | Client-Side Rendering |
| Language | JavaScript |
| Paywall | No |
0 Comments