Bird
Raised Fist0
Gitdevops~5 mins

Global vs local configuration in Git - Performance Comparison

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Time Complexity: Global vs local configuration
O(n)
Understanding Time Complexity

When using git, configuration settings can be global or local. Understanding how git reads these settings helps us see how time grows when many configs exist.

We want to know: How does git find the right setting as configurations increase?

Scenario Under Consideration

Analyze the time complexity of git reading configuration values.


# Show global config
$ git config --global user.name

# Show local config
$ git config --local user.name

# Set local config
$ git config --local user.email "user@example.com"

# Read config (git checks local then global)
$ git config user.name

This code shows how git reads and sets user info in global and local configs.

Identify Repeating Operations

Git looks for config values by checking files in order.

  • Primary operation: Reading config files one by one.
  • How many times: Once per config file until value found or all checked.
How Execution Grows With Input

As the number of config files grows, git checks each file in order.

Input Size (number of config files)Approx. Operations (file checks)
2Up to 2 file reads
5Up to 5 file reads
10Up to 10 file reads

Pattern observation: The more config files, the more files git checks one by one.

Final Time Complexity

Time Complexity: O(n)

This means git's time to find a config grows linearly with the number of config files it checks.

Common Mistake

[X] Wrong: "Git reads all config files instantly no matter how many there are."

[OK] Correct: Git reads files one by one until it finds the setting, so more files mean more checks and more time.

Interview Connect

Understanding how git reads configs helps you think about how tools handle layered settings. This skill shows you can analyze how processes grow with input size.

Self-Check

"What if git cached config values after first read? How would the time complexity change?"

Practice

(1/5)
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 "user@example.com"
B. git config --system user.email "user@example.com"
C. git config user.email "user@example.com"
D. git set user.email "user@example.com"

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 "user@example.com" is the simplest correct form.

  3. Final Answer:

    git config user.email "user@example.com" -> 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 "global@example.com"
git config --local user.email "project@example.com" (inside project)
B. git config --local user.email "global@example.com"
git config --global user.email "project@example.com"
C. git config user.email "global@example.com" (inside project)
git config --global user.email "project@example.com"
D. git config --global user.email "project@example.com"
git config user.email "global@example.com" (inside project)

Solution

  1. Step 1: Set global email first

    Use git config --global user.email "global@example.com" 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 "project@example.com" to override the global email only for that project.

  3. Final Answer:

    git config --global user.email "global@example.com" followed by git config --local user.email "project@example.com" 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