Creating aliases for common commands in Git - Step-by-Step CLI Walkthrough

Introduction

Typing long commands repeatedly can be slow and error-prone. Aliases let you create short nicknames for common git commands to save time and avoid mistakes.

When you often run 'git status' and want a shorter command like 'git st'.

When you want to combine multiple git commands into one easy shortcut.

When you want to customize git commands to your workflow without typing full commands.

When you want to share your favorite git shortcuts with teammates.

When you want to speed up your daily git work by reducing typing.

Commands

This command creates a global alias 'st' for 'status'. Now you can type 'git st' instead of 'git status'.

Terminal

git config --global alias.st status

Expected Output

No output (command runs silently)

→

--global - Sets the alias for all repositories for the current user.

Runs the alias 'st' which executes 'git status' to show the current state of the repository.

Terminal

git st

Expected Output

On branch main

Your branch is up to date with 'origin/main'.



nothing to commit, working tree clean

Creates a global alias 'co' for 'checkout' to switch branches faster.

Terminal

git config --global alias.co checkout

Expected Output

No output (command runs silently)

→

--global - Applies alias globally for the user.

Uses the alias 'co' to create and switch to a new branch named 'feature-branch'.

Terminal

git co -b feature-branch

Expected Output

Switched to a new branch 'feature-branch'

Key Concept

If you remember nothing else from this pattern, remember: git aliases save time by letting you use short commands for longer git operations.

Common Mistakes

Creating an alias without the 'git' prefix when running it.

Git aliases must be run as 'git aliasname', not just 'aliasname' alone.

Always run aliases with 'git' before the alias, like 'git st'.

Setting aliases without the --global flag and expecting them to work in all repos.

Without --global, aliases apply only to the current repository.

Use --global to make aliases available in all your git repositories.

Trying to alias commands with arguments included (like 'git config alias.co checkout -b').

Git aliases only alias commands, not arguments or flags.

Alias only the base command, then add arguments when running the alias.

Summary

Use 'git config --global alias.name command' to create a shortcut alias.

Run aliases with 'git aliasname' to save typing long commands.

Use --global flag to make aliases available in all repositories.

Practice

1. What is the main purpose of creating aliases in Git?

easy

A. To change the Git version

B. To delete branches automatically

C. To create new repositories

D. To make commands shorter and easier to type

Solution

1. Step 1: Understand what aliases do

   Aliases are shortcuts that replace longer commands with shorter names.

2. Step 2: Identify the main benefit

   Shorter commands save time and reduce typing effort.

3. Final Answer:

   To make commands shorter and easier to type -> Option D

4. Quick Check:

   Aliases = Shorter commands [OK]

Hint: Aliases shorten commands for faster typing [OK]

Common Mistakes:

• Thinking aliases change Git versions
• Confusing aliases with deleting branches
• Believing aliases create repositories

2. Which of the following is the correct syntax to create a global alias named st for status in Git?

easy

A. git config alias.st status --global

B. git alias --global st status

C. git config --global alias.st status

D. git create alias st status

Solution

1. Step 1: Recall the alias creation syntax

   The correct syntax is git config --global alias.name 'command'.

2. Step 2: Match the syntax to the options

   git config --global alias.st status matches the correct syntax exactly.

3. Final Answer:

   git config --global alias.st status -> Option C

4. Quick Check:

   Correct syntax = git config --global alias.st status [OK]

Hint: Use 'git config --global alias.name command' format [OK]

Common Mistakes:

• Placing --global after alias name
• Using 'git alias' instead of 'git config'
• Incorrect command order

3. Given the alias creation command git config --global alias.co checkout, what will be the output of git co?

medium

A. Runs the 'checkout' command

B. Throws an error: unknown command

C. Displays the commit history

D. Shows the current branch status

Solution

1. Step 1: Understand the alias mapping

   The alias 'co' is set to run the 'checkout' command.

2. Step 2: Predict the effect of 'git co'

   Typing 'git co' runs 'git checkout'.

3. Final Answer:

   Runs the 'checkout' command -> Option A

4. Quick Check:

   Alias 'co' = 'checkout' command [OK]

Hint: Alias runs the mapped command exactly [OK]

Common Mistakes:

• Confusing 'co' with 'status'
• Expecting output instead of command execution
• Assuming alias causes error

4. You tried to create an alias with git config --global alias.br branch -a but typing git br gives an error. What is the most likely mistake?

medium

A. Alias command was not saved due to missing quotes

B. Alias was created locally, not globally

C. You need to restart Git to apply aliases

D. The alias name 'br' is reserved and cannot be used

Solution

1. Step 1: Check alias creation syntax

   Quotes around the command are needed to save the alias properly.

2. Step 2: Identify the error cause

   Missing or incorrect quotes cause the alias not to save, leading to errors when used.

3. Final Answer:

   Alias command was not saved due to missing quotes -> Option A

4. Quick Check:

   Missing quotes = alias not saved [OK]

Hint: Always quote the command when creating aliases [OK]

Common Mistakes:

• Assuming alias applies without quotes
• Thinking Git needs restart for aliases
• Believing alias names are reserved

5. You want to create a Git alias named lg that shows a pretty log graph with one command. Which of these commands correctly creates this alias?

hard

A. git config alias.lg 'log --graph --oneline --all' --global

B. git config --global alias.lg "log --graph --oneline --all"

C. git alias --global lg 'log --graph --oneline --all'

D. git config --global alias.lg log --graph --oneline --all

Solution

1. Step 1: Recall correct alias syntax with multiple options

   Use quotes to include all options as one command string.

2. Step 2: Identify the correct command format

   git config --global alias.lg "log --graph --oneline --all" uses correct syntax with double quotes and global flag first.

3. Final Answer:

   git config --global alias.lg "log --graph --oneline --all" -> Option B

4. Quick Check:

   Quotes + --global first = correct alias command [OK]

Hint: Quote full command string and use --global first [OK]

Common Mistakes:

• Placing --global after alias name
• Not quoting multi-option commands
• Using 'git alias' instead of 'git config'