Git Configuration & Aliases

Five minutes of setup makes Git faster and friendlier forever. By the end of this lesson you'll have configured your identity, picked your editor, and built a set of short aliases that turn long commands into two-letter shortcuts.

Learn Git Configuration & Aliases in our free Git course — a beginner-friendly interactive lesson with worked examples, a practice exercise and a quick…

Part of the free Git course at LearnCodingFast — hands-on lessons with examples you run in your browser, plus practice exercises and a quick quiz.

What You'll Learn

1️⃣ Set Your Identity

Git stamps every commit with a name and email. Set them once with --global so they apply to all your repos. Use the same email as your GitHub account so your commits link back to your profile.

2️⃣ The Three Scopes

Config exists at three levels: --system (all users), --global (all your repos), and --local (just this repo, the default). Git reads them in that order, so the most specific value wins — handy for using a work email in one repo while keeping your usual one everywhere else.

3️⃣ Aliases — Your Own Shortcuts

Aliases live under the [alias] section and turn long commands into short ones. Define st , co , lg and use them like real subcommands. Start an alias value with ! to run a full shell command.

Your turn. Set your name globally and add a one-letter status alias. Fill in the two blanks.

4️⃣ Editor & Other Handy Settings

A few one-time settings smooth everything out: core.editor picks the editor Git opens, init.defaultBranch names the starting branch for new repos, and color.ui turns on colour. Remove any setting with --unset .

Common Errors (and the fix)

• Commits show the wrong author: a local override is in play, or identity was unset. Run git config --list --show-origin and fix or --unset the offending value.
• Editor never opens / hangs: a GUI editor without --wait returns immediately, so Git thinks you wrote nothing. Use core.editor "code --wait" .
• Alias does nothing or errors: you may have set it locally in a different repo, or the value needs quotes. Multi-word values must be quoted: alias.lg "log --oneline" .
• "command not found" from a ! alias: shell aliases run from the repo root and need the tools on your PATH — test the raw command first.
• Forgetting --global: without it, git config writes to the current repo only, so the setting "disappears" in other repos.

Pro Tips

• 💡 Edit the file directly: git config --global --edit opens ~/.gitconfig for bulk changes.
• 💡 Great starter aliases: st=status , co=checkout , lg=log --oneline --graph --all , last=log -1 HEAD .
• 💡 Per-directory identity: use a conditional include ( includeIf "gitdir:~/work/" ) to auto-switch your work email.
• 💡 Sync across machines: keep your ~/.gitconfig in a dotfiles repo.

📋 Quick Reference

Command

Purpose

git config --global user.name "X"

Set your commit name everywhere

git config --global alias.st status

Create the alias git st

git config --list --show-origin

List all values and their files

git config --global core.editor "..."

Choose your editor

git config --global init.defaultBranch main

Name the starting branch

git config --unset key

Remove a setting

Frequently Asked Questions

Mini-Challenge: Build Your Starter Config

No commands given this time — just the plan. Configure a fresh machine the way a pro would, all in your global config.

🎉 Lesson Complete!

• ✅ --global sets your identity and prefs for every repo
• ✅ Three scopes — system, global, local — with the most specific winning
• ✅ Aliases turn long commands into short ones; ! runs a shell command
• ✅ core.editor and init.defaultBranch are worth setting once
• ✅ --list --show-origin debugs surprising values
• ✅ Next lesson: push a branch and open your first GitHub pull request

Practice quiz

Continue this course

• Previous: Hunting Bugs with git bisect
• Next: GitHub Pull Requests & Code Review