How do you configure Git and use aliases?

Question

IT Interview Practice · Accepted Answer

Git is highly **configurable** via `git config` — setting your identity, editor, default behaviors, and **aliases** (shortcuts for commands). Configuring Git well and using aliases improves your workflow and productivity.

## Essential configuration

```bash
# identity (required — appears in your commits)
git config --global user.name "Your Name"
git config --global user.email "you@example.com"

# common useful settings
git config --global core.editor "code --wait"   # editor for commit messages
git config --global init.defaultBranch main      # default branch name
git config --global pull.rebase true             # rebase instead of merge on pull
git config --global core.autocrlf input          # line-ending handling (cross-platform)
```

```text
CONFIG LEVELS (each overrides the broader one):
  --system → all users on the machine
  --global → your user (most common: ~/.gitconfig)
  --local  → this repository (.git/config) — overrides global
```

## Aliases — command shortcuts

```bash
# define shortcuts for frequently-used (or long) commands
git config --global alias.co checkout
git config --global alias.br branch
git config --global alias.st status
git config --global alias.cm "commit -m"
git config --global alias.last "log -1 HEAD"
git config --global alias.lg "log --oneline --graph --all"
# usage:
git st           # = git status
git lg           # = git log --oneline --graph --all (a nice history view)
```

Aliases turn long or frequent commands into short shortcuts — `git lg` for a formatted log, `git st` for status — saving keystrokes and effort.

## Why config matters

```text
✓ Identity → correct author info on commits (required)
✓ Behaviors → pull.rebase, autocrlf, default branch → consistent, fewer surprises
✓ Aliases → faster workflow for frequent/complex commands
✓ Per-repo config → e.g. a different email for work vs personal repos (--local)
```

## Why it matters

Understanding Git configuration and aliases is valuable for **improving your Git workflow and productivity**, so it's useful practical knowledge. **Essential configuration** is necessary correctness: setting your **identity** (`user.name`/`user.email`) is required since it appears in your commits (and misconfigured identity causes commits attributed wrongly — a common issue), and configuring useful **behaviors** (editor, default branch name, pull behavior like `pull.rebase`, line-ending handling with `autocrlf` for cross-platform teams) makes Git behave consistently and avoids surprises.

Understanding the **config levels** (system, global, local — each overriding the broader, with local being per-repository) is practically valuable, notably for using **different settings per repository** (like a work email for work repos vs a personal email — a common real need). **Aliases** improve productivity by turning frequent or long commands into short shortcuts (`git st` for status, `git lg` for a nicely-formatted graph log) — small but meaningful efficiency gains given how constantly Git commands are used, and a way to make complex, useful command combinations easily accessible.

Understanding how to configure Git well (correct identity, sensible behaviors, per-repo settings) and use aliases (faster, more pleasant workflow) reflects a polished, efficient approach to daily Git use.

Since Git is used constantly and configuring it properly (identity, behaviors, per-repo settings) ensures correctness and consistency while aliases improve everyday efficiency, understanding Git configuration and aliases is valuable, practically-relevant knowledge for an effective Git workflow — useful for both correctness (proper identity and behaviors) and productivity (aliases for frequent commands), a worthwhile investment for anyone who uses Git regularly and a sign of a developer who has tuned their tools for efficient daily work.

Essential configuration

Aliases — command shortcuts

Why config matters

Why it matters

Related questions