DevOps & Dev Utilities

Git Command Reference

Look up the Git command you half-remember, filtered by category — setup, staging, commits, branches, remotes, stash, and tags.

Free & unlimitedRuns in your browserNo sign-up required

Command	Description
`git init`	Initialize a new local repository
`git clone <url>`	Clone a remote repository locally
`git status`	Show working tree status
`git add .`	Stage all changes for commit
`git add <file>`	Stage a specific file
`git commit -m "msg"`	Commit staged changes with a message
`git commit --amend`	Modify the most recent commit
`git log --oneline`	Compact commit history
`git diff`	Show unstaged changes
`git diff --staged`	Show staged (cached) changes

Git Workflow Essentials

Git is the world's most widely used distributed version control system, powering the development workflows of millions of engineers at companies ranging from solo startups to global enterprises.

The three states of Git

Files in Git exist in three states: Modified (changed but not committed), Staged (marked for the next commit), and Committed (safely stored in your local repository). Understanding this transition — working directory → staging area → repository — is fundamental to mastering Git.

Branching strategies

Git Flow uses long-lived develop and main branches with feature/, release/, and hotfix/ prefixes. GitHub Flow uses a simpler model: everything branches from main, gets reviewed as a pull request, and merges directly to main. Trunk-based development skips long-lived feature branches entirely in favor of frequent small commits to main.

Writing good commit messages

The conventional commits standard (feat:, fix:, docs:, refactor:) enables automatic changelog generation and semantic versioning. The subject line should be 50 characters or fewer, in the imperative mood: "Add user authentication" not "Added user authentication".

Interactive rebase best practices

Use git rebase -i to squash work-in-progress commits before merging a feature branch, keeping history clean and readable. Never rebase commits that have already been pushed to a shared remote branch — this rewrites history and forces other team members to reconcile conflicts.

Loading tool…

How it works

Three steps, no setup

Search or filter by category

Jump straight to branching, remotes, or stash commands.

Read the description

Each command includes a plain-language explanation of what it does.

Copy and run it

Paste directly into your terminal.

Common questions

Frequently asked questions

Is this a full Git manual?

It covers the commands developers reach for daily rather than every flag and edge case — for exhaustive detail, the official Git documentation is the deeper reference.

Are dangerous commands flagged?

Commands that rewrite history or discard changes, like reset --hard, are called out so you know to use them carefully.

Keep exploring

Related tools

View all tools

DevOps & Dev Utilities

Git Command Reference

Git Workflow Essentials

The three states of Git

Branching strategies

Writing good commit messages

Interactive rebase best practices

Three steps, no setup

Search or filter by category

Read the description

Copy and run it

Frequently asked questions

Related tools

Docker Run to Compose Converter

Chmod Permission Calculator

JavaScript Benchmark Builder

Keyboard Event Inspector

Browser & Device Inspector

Framer Site HTML Exporter

twoworks

Git Workflow Essentials

The three states of Git

Branching strategies

Writing good commit messages

Interactive rebase best practices