Global vs local configuration in Git - CLI Comparison

Introduction

Git lets you set configuration options that control how it works. These settings can be saved globally for all projects or locally for just one project. This helps you customize Git behavior depending on your needs.

When you want your name and email to be the same for all your Git projects on your computer

When you need a different username or email for a specific project, like work vs personal

When you want to change Git settings like line endings or merge tools only for one project

When you want to check what settings are active in your current project

When you want to fix a problem caused by wrong Git settings in one project without affecting others

Commands

This sets your name globally for all Git projects on your computer. Git uses this name in commits unless overridden locally.

Terminal

git config --global user.name "Alice Smith"

Expected Output

No output (command runs silently)

→

--global - Sets the configuration for all projects for the current user

This sets your email globally for all Git projects. It is used in commits to identify the author.

Terminal

git config --global user.email "[e-mail]"

Expected Output

No output (command runs silently)

→

--global - Applies the setting to all repositories for the user

This sets your name only for the current Git project. It overrides the global name for this project.

Terminal

git config --local user.name "Alice Work"

Expected Output

No output (command runs silently)

→

--local - Sets the configuration only for the current repository

Shows all Git configuration settings currently active in the current project, including global and local ones.

Terminal

git config --list

Expected Output

user.name=Alice Work

user.email=[e-mail]

Removes the local user.name setting, so Git will use the global name again in this project.

Terminal

git config --local --unset user.name

Expected Output

No output (command runs silently)

→

--unset - Removes a configuration setting

→

--local - Targets the local repository configuration

Key Concept

Local Git settings override global settings for the current project only.

Common Mistakes

Setting user.name without --global or --local flags

Git may set the value in an unexpected config file or fail silently, causing confusion about which setting is active.

Always specify --global to set for all projects or --local to set for the current project explicitly.

Assuming global settings apply when local settings exist

Local settings take priority, so global settings are ignored in that project, leading to unexpected author info in commits.

Check local settings with git config --list and remove local overrides if you want global settings to apply.

Summary

Use git config --global to set options for all your Git projects on your computer.

Use git config --local to set options only for the current project, overriding global settings.

Check active settings with git config --list to see which values Git uses in the current project.

Practice

1. What is the main difference between git config --global and git config --local?

easy

A. Local config is stored in the user's home directory.

B. Global config applies only to the current project; local config applies to all projects.

C. Global config overrides local config settings.

D. Global config applies to all projects; local config applies only to the current project.

Solution

1. Step 1: Understand global configuration scope

   Global configuration applies settings to all Git projects on the computer, stored in the user's home directory.

2. Step 2: Understand local configuration scope

   Local configuration applies only to the current Git project and overrides global settings if both exist.

3. Final Answer:

   Global config applies to all projects; local config applies only to the current project. -> Option D

4. Quick Check:

   Global = all projects, Local = current project [OK]

Hint: Global is for all projects, local is project-specific [OK]

Common Mistakes:

• Confusing which config applies globally or locally
• Thinking local config is stored in home directory
• Assuming global config overrides local config

2. Which of the following commands correctly sets the user email only for the current Git project?

easy

A. git config --global user.email "[e-mail]"

B. git config --system user.email "[e-mail]"

C. git config user.email "[e-mail]"

D. git set user.email "[e-mail]"

Solution

1. Step 1: Identify the correct command for local config

   By default, git config without --global or --system sets local config for the current project.

2. Step 2: Check command syntax

   git config --local is valid but optional; git config user.email "[e-mail]" is the simplest correct form.

3. Final Answer:

   git config user.email "[e-mail]" -> Option C

4. Quick Check:

   Local config uses git config without --global [OK]

Hint: Use git config without --global for local settings [OK]

Common Mistakes:

• Using --global when wanting local config
• Using invalid command like git set
• Assuming --local is mandatory

3. Given these commands run in order inside a Git project:

git config --global user.name "GlobalUser"
git config user.name "LocalUser"
git config user.name

What will be the output of the last command?

medium

A. GlobalUser

B. LocalUser

C. No output (empty)

D. Error: user.name not set

Solution

1. Step 1: Understand config precedence

   Local config overrides global config when both exist for the same key.

2. Step 2: Analyze the commands

   First sets global user.name to "GlobalUser", then local user.name to "LocalUser". The last command reads the effective user.name, which is local.

3. Final Answer:

   LocalUser -> Option B

4. Quick Check:

   Local overrides global, so output is LocalUser [OK]

Hint: Local config overrides global for same key [OK]

Common Mistakes:

• Assuming global config always shows
• Thinking last set value globally is used
• Confusing output with error

4. You ran git config --local user.name "Alice" but git config user.name still shows "Bob". What is the most likely problem?

medium

A. You are not inside a Git repository directory.

B. You used --local incorrectly; it should be --global.

C. The global config is overriding the local config.

D. The user.name key is misspelled.

Solution

1. Step 1: Check local config requirements

   Local config applies only inside a Git repository folder. Outside, local config commands fail silently or do not apply.

2. Step 2: Understand why global shows instead

   If outside a repo, local config is ignored, so global config value "Bob" is shown.

3. Final Answer:

   You are not inside a Git repository directory. -> Option A

4. Quick Check:

   Local config needs repo folder [OK]

Hint: Local config works only inside a Git repo folder [OK]

Common Mistakes:

• Assuming global always overrides local
• Using wrong option --global instead of --local
• Misspelling config keys

5. You want to set your Git user email globally but override it with a different email for a specific project. Which sequence of commands achieves this?

hard

A. git config --global user.email "[e-mail]"git config --local user.email "[e-mail]" (inside project)

B. git config --local user.email "[e-mail]"git config --global user.email "[e-mail]"

C. git config user.email "[e-mail]" (inside project)git config --global user.email "[e-mail]"

D. git config --global user.email "[e-mail]"git config user.email "[e-mail]" (inside project)

Solution

1. Step 1: Set global email first

   Use git config --global user.email "[e-mail]" to set the default email for all projects.

2. Step 2: Override locally inside the project

   Inside the project folder, run git config --local user.email "[e-mail]" to override the global email only for that project.

3. Final Answer:

   git config --global user.email "[e-mail]" followed by git config --local user.email "[e-mail]" inside project -> Option A

4. Quick Check:

   Global first, then local override inside project [OK]

Hint: Set global first, then local inside project to override [OK]

Common Mistakes:

• Setting local config before global
• Using local config outside project folder
• Confusing which email applies where