What is the difference between --global and --local?

--global applies to all repos on your user account (stored in ~/.gitconfig). --local applies only to the current repo (stored in .git/config). Local config takes priority over global.

How do I view all Git configuration?

Run git config --list to see all configured values (system + global + local). To see only global config: git config --global --list. To find where a value comes from: git config --show-origin user.name.

How do I create Git aliases?

Use git config --global alias.name "command". For example: git config --global alias.co checkout. Then you can type git co instead of git checkout. Most common aliases: co (checkout), br (branch), ci (commit), st (status).

How do I change the default Git editor?

Run git config --global core.editor "editor-name". Examples: "code --wait" for VS Code, "nano" for Nano, "vim" for Vim. The --wait option is important for VS Code as it tells Git to wait until you close the file.

How do I remove a configuration value?

Use git config --global --unset key.name. For example: git config --global --unset alias.co to remove the "co" alias. To remove an entire section: git config --global --remove-section alias.

Git config: configure Git your way

Before you start using Git, you need to configure it. Name, email, editor, aliases: this page explains how to customize Git so it works the way you want.

Practice Git Git Glossary

gitquest — enquête

The 3 configuration levels

Git manages configuration at three levels. The most specific level always takes priority.

Level 1

--system

Applies to all users on the machine. Rarely modified manually.

/etc/gitconfig

Level 2

--global

Applies to all repos on your account. This is the most commonly used level for personal config.

~/.gitconfig

Level 3

--local

Applies only to the current repo. Useful for having a different work email per project.

.git/config

Git config in practice

Essential setup and creating aliases to save time.

Basic configuration

gitquest — config

# Essential setup (do this once)

$git config --global user.name "Anais Sparesotto"

$git config --global user.email "anais@example.com"

Name and email configured for all your repos

# Change the default editor

$git config --global core.editor "code --wait"

# Set the default branch to "main"

$git config --global init.defaultBranch main

# Enable pull --rebase by default

$git config --global pull.rebase true

Aliases and overview

gitquest — alias

# Create aliases to speed things up

$git config --global alias.co checkout

$git config --global alias.br branch

$git config --global alias.ci commit

$git config --global alias.st status

$git config --global alias.lg "log --oneline --graph --all"

Aliases created! Type git co, git br, git st...

# View all configuration

$git config --list

user.name=Anais Sparesotto

user.email=anais@example.com

core.editor=code --wait

alias.co=checkout

alias.st=status

Essential configuration settings

user.name

Your name, displayed in every commit. Required to commit.

git config --global user.name "Your Name"

user.email

Your email, associated with every commit. Use the one from your GitHub account.

git config --global user.email "your@email.com"

core.editor

The editor Git opens (for commit messages, interactive rebase, etc.).

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

init.defaultBranch

The default branch name when running git init. The modern convention is "main".

git config --global init.defaultBranch main

pull.rebase

Enables automatic rebase during git pull, for a linear history.

git config --global pull.rebase true

alias.*

Create shortcuts for long commands. Essential for working faster.

git config --global alias.st status

Configuration tips

Set up your name and email first

This is required to commit. Do it once with --global and it's set for all your projects.

Use --local for work projects

If you have a personal email set globally, use --local in your work projects to associate your professional email.

Create aliases from the start

Aliases like git st, git co and git lg will save you time every day.

Back up your .gitconfig

The ~/.gitconfig file contains all your global config. Save it in a "dotfiles" repo to restore your setup on a new machine.

Part of the Git Advanced guide

Related commands

git init

Initialize a repository

git remote

Configure remote repositories

git commit

Use config for commits

GitQuest is created by Anaïs (nouvelle fenêtre), web developer and head of education, specializing in tech training and digital accessibility.

Questions about git config

Configure Git and start practicing

Once Git is configured, dive into GitQuest investigations to learn commands in real-world scenarios.

Start the investigations