Creating aliases for common commands in Git - Try It Yourself

Creating aliases for common commands

📖 Scenario: You often use Git commands to manage your code projects. Typing long commands repeatedly can be tiring. To save time, you want to create shortcuts called aliases for your most common Git commands.

🎯 Goal: Learn how to create Git aliases to run common commands faster by typing short words instead of full commands.

📋 What You'll Learn

Create a Git alias for the git status command

Create a Git alias for the git log --oneline command

Create a Git alias for the git checkout command

Display the list of all Git aliases to verify your setup

💡 Why This Matters

🌍 Real World

Developers use Git aliases daily to speed up their workflow and avoid typing long commands repeatedly.

💼 Career

Knowing how to create and manage Git aliases is a useful skill for software developers, DevOps engineers, and anyone working with version control.

1

Create an alias for git status

Use the command git config --global alias.st status to create a Git alias called st that runs git status.

Git

# Your code here

Hint

This command sets a shortcut st for git status globally on your computer.

2

Create an alias for git log --oneline

Use the command git config --global alias.lg "log --oneline" to create a Git alias called lg that runs git log --oneline.

Git

git config --global alias.st status
# Your code here

Hint

Use quotes around log --oneline because it has a space.

3

Create an alias for git checkout

Use the command git config --global alias.co checkout to create a Git alias called co that runs git checkout.

Git

git config --global alias.st status
git config --global alias.lg "log --oneline"
# Your code here

Hint

This alias lets you type git co instead of git checkout.

4

Display all Git aliases

Run the command git config --global --get-regexp alias to show all your Git aliases and verify they are set correctly.

Git

git config --global alias.st status
git config --global alias.lg "log --oneline"
git config --global alias.co checkout
# Your code here

Hint

This command lists all aliases starting with alias..

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'