How do I apply these aliases?

Copy the generated block and paste it into your ~/.gitconfig file (global) or .git/config file (per-repository). If an [alias] section already exists, merge the lines into it rather than adding a duplicate section header.

Will these aliases conflict with built-in Git commands?

Git aliases only trigger when the name does not match a built-in subcommand. All aliases provided here use short names (e.g. st, co, lg) that are not built-in Git commands, so there is no conflict.

Can I rename an alias key?

Yes. Each alias has an editable key field in the tool. Change the key to whatever short name you prefer and the output block updates immediately.

What does the ! prefix mean in some alias values?

A ! prefix tells Git to run the value as a shell command rather than a Git subcommand. For example, !git fetch --all && git rebase runs two commands in sequence. This is standard Git behavior and is safe to use.

Where is my .gitconfig file?

On Linux and macOS it is at ~/.gitconfig. On Windows it is typically at C:\Users\YourName\.gitconfig. You can also run "git config --global --edit" to open it in your default editor.

Git Alias Cheatsheet Generator

Pick the Git aliases you want, then copy the ready-to-paste [alias] block for your .gitconfig file.

0 selected

.gitconfig output

Summary

Select from a curated list of popular Git aliases covering status, logging, branching, stashing, and more. The tool instantly generates a [alias] section you can paste into ~/.gitconfig or a project-level .git/config. All processing is local — nothing is sent to a server.

How it works

Browse the alias catalog grouped by category.
Check any aliases you want to include — or click "Select All" for a category.
Optionally rename the short alias key in the input field.
The [alias] block on the right updates in real time.
Click "Copy to Clipboard" to copy the block, then paste it into your .gitconfig.

Use cases

Setting up a productive Git workflow on a new machine.
Sharing a standard set of shortcuts with a team via a dotfiles repository.
Learning Git by exploring what common alias shortcuts expand to.
Reducing repetitive typing for frequently used multi-flag commands.
Onboarding junior developers with a curated set of readable shortcuts.
Building a project-level .git/config with repo-specific aliases.

Frequently Asked Questions

Last updated: 2026-05-23 · Reviewed by Nham Vu