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.