Creating aliases for common commands in Git - Practice Exercises

Challenge - 5 Problems

💻 Command Output

intermediate

Output of a Git alias command

What is the output of running git co after setting the alias co to checkout?

Git

git config --global alias.co checkout
git co -b new-branch

A Lists all branches in the repository.

B Shows an error: 'git: 'co' is not a git command.'

C Deletes the branch named 'new-branch'.

D Creates and switches to a new branch named 'new-branch'.

💡 Hint

Think about what 'checkout -b' does in Git.

The alias 'co' replaces 'checkout'. The command 'git co -b new-branch' creates and switches to a new branch named 'new-branch'.

❓ Configuration

intermediate

Correct syntax for setting a Git alias

Which command correctly sets a Git alias named st for status?

A git config --global alias.st status

B git alias set st status

C git config alias.st=status

D git set alias st status

💡 Hint

Git aliases are set using the config command with 'alias.' prefix.

The correct syntax uses 'git config --global alias.st status' to set the alias globally.

❓ Troubleshoot

advanced

Troubleshooting a Git alias that does not work

You set a Git alias lg as log --oneline --graph but running git lg gives an error. What is the most likely cause?

Git

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

A The alias command must be set without quotes around the value.

B The alias should not include spaces; use a shell script instead.

C The alias is correct; the error is due to missing Git repository.

D The alias command needs double quotes instead of single quotes.

💡 Hint

Check how Git stores alias commands in the config file.

Git aliases should be set without quotes around the command. Quotes become part of the alias and cause errors.

🔀 Workflow

advanced

Using Git aliases in a workflow

You have these aliases set:
git config --global alias.co checkout
git config --global alias.br branch
Which sequence of commands uses these aliases to create and switch to a new branch named feature and then list all branches?

A git checkout feature && git branch -a

B git co -b feature && git br

C git br -b feature && git co

D git br feature && git co -a

💡 Hint

Remember what 'checkout -b' and 'branch' commands do.

'git co -b feature' creates and switches to 'feature'. 'git br' lists branches. This uses the aliases correctly.

✅ Best Practice

expert

Best practice for naming Git aliases

Which of the following is the best practice when naming Git aliases for common commands?

A Use names that match existing Git commands to override them for customization.

B Use long descriptive names to avoid confusion, even if they are hard to type.

C Use short, memorable names that do not conflict with existing Git commands.

D Use random letters to ensure uniqueness, regardless of readability.

💡 Hint

Think about ease of use and avoiding errors.

Short, memorable aliases that do not conflict with Git commands help avoid confusion and improve efficiency.

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'