Bird
Raised Fist0
Gitdevops~5 mins

Git configuration (user.name, user.email) - Cheat Sheet & Quick Revision

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
Recall & Review
beginner
What is the purpose of git config user.name?
It sets the name that will appear as the author of your commits in Git.
Click to reveal answer
beginner
What does git config user.email do?
It sets the email address that will be associated with your commits in Git.
Click to reveal answer
beginner
How do you set your Git username globally for all repositories?
Use the command git config --global user.name "Your Name".
Click to reveal answer
beginner
How can you check your current Git user name and email?
Run git config user.name and git config user.email to see the current settings.
Click to reveal answer
intermediate
What is the difference between setting Git config with and without --global?
With --global, the setting applies to all repositories for your user. Without it, the setting applies only to the current repository.
Click to reveal answer
Which command sets your Git email globally?
Agit email set --global "you@example.com"
Bgit set user.email "you@example.com"
Cgit config user.email --global "you@example.com"
Dgit config --global user.email "you@example.com"
What happens if you set user.name without --global?
AIt sets the username for all repositories.
BIt sets the username only for the current repository.
CIt deletes the global username.
DIt sets the username for all users on the computer.
How do you view your current Git username?
Agit config user.name
Bgit show user.name
Cgit get user.name
Dgit user.name
Why is it important to set user.email in Git?
AIt sets the repository URL.
BIt controls repository access.
CIt identifies the author of commits.
DIt changes the branch name.
Which file stores the global Git configuration?
A~/.gitconfig
B.git/config
C/etc/gitconfig
Dconfig/global.git
Explain how to set your Git username and email globally and why it matters.
Think about how Git tracks who makes changes.
You got /4 concepts.
    Describe the difference between global and local Git configuration for user.name and user.email.
    Consider scope and command syntax.
    You got /4 concepts.

      Practice

      (1/5)
      1. What is the purpose of setting user.name and user.email in Git configuration?
      easy
      A. To set the default branch name
      B. To enable Git debugging mode
      C. To configure the remote repository URL
      D. To label your commits with your identity

      Solution

      1. Step 1: Understand Git commit metadata

        Git uses user.name and user.email to identify who made each commit.

      2. Step 2: Recognize the role of these settings

        These settings label your work so others know who made changes.

      3. Final Answer:

        To label your commits with your identity -> Option D

      4. Quick Check:

        user.name and user.email = commit identity [OK]
      Hint: Remember: name and email tag your commits [OK]
      Common Mistakes:
      • Confusing user.name with branch name
      • Thinking user.email sets remote URL
      • Assuming these enable debugging
      2. Which command correctly sets your global Git user email to "user@example.com"?
      easy
      A. git config --email user@example.com --global
      B. git config --global user.email user@example.com
      C. git config user.email --global user@example.com
      D. git set user.email global user@example.com

      Solution

      1. Step 1: Recall correct Git config syntax

        The correct syntax is git config --global key value.

      2. Step 2: Match the command to set user.email globally

        git config --global user.email user@example.com matches this syntax exactly.

      3. Final Answer:

        git config --global user.email user@example.com -> Option B

      4. Quick Check:

        git config --global key value sets global config [OK]
      Hint: Use 'git config --global key value' format [OK]
      Common Mistakes:
      • Swapping order of flags and values
      • Using 'git set' instead of 'git config'
      • Placing --global after the key
      3. Given these commands run in order:
      git config --global user.name "Alice"
git config user.name "Bob"

      What will git config user.name output inside the current repository?
      medium
      A. Bob
      B. No output (empty)
      C. Alice
      D. Error: user.name not set

      Solution

      1. Step 1: Understand global vs local config

        The first command sets user.name globally to "Alice". The second sets it locally to "Bob" in the current repo.

      2. Step 2: Determine which config is used

        Local config overrides global inside the repo, so git config user.name shows "Bob".

      3. Final Answer:

        Bob -> Option A

      4. Quick Check:

        Local config overrides global config [OK]
      Hint: Local config overrides global config [OK]
      Common Mistakes:
      • Assuming global always overrides local
      • Expecting empty output if local set
      • Confusing command order effects
      4. You run git config user.email "wrongemail.com" but your commits still show the old email. What is the likely problem?
      medium
      A. You forgot to add --global or --local, so it set config in an unexpected scope
      B. The email format is invalid, so Git ignored the setting
      C. You need to restart Git for changes to apply
      D. Git does not allow changing user.email once set

      Solution

      1. Step 1: Check command scope

        Without --global or --local, Git sets config in the current repo (local) by default.

      2. Step 2: Understand why commits show old email

        If commits show old email, likely you changed config in a different scope than where commits are made.

      3. Final Answer:

        You forgot to add --global or --local, so it set config in an unexpected scope -> Option A

      4. Quick Check:

        Config scope matters; missing flags cause confusion [OK]
      Hint: Always specify --global or --local to avoid confusion [OK]
      Common Mistakes:
      • Assuming Git ignores invalid emails silently
      • Thinking Git needs restart after config change
      • Believing user.email is immutable
      5. You want to set different user names and emails for two projects on the same computer. How do you configure Git correctly?
      hard
      A. Set user.name and user.email only locally in one project; global config is ignored
      B. Set user.name and user.email only globally; Git automatically detects project differences
      C. Set global user.name and user.email once, then override locally per project with git config user.name and git config user.email
      D. Use environment variables instead of Git config to set user identity

      Solution

      1. Step 1: Understand global and local config roles

        Global config applies to all repos unless overridden locally.

      2. Step 2: Apply local overrides per project

        Set local user.name and user.email in each project to customize identity per repo.

      3. Final Answer:

        Set global user.name and user.email once, then override locally per project with git config user.name and git config user.email -> Option C

      4. Quick Check:

        Global sets default; local overrides per project [OK]
      Hint: Global sets default; local overrides per project [OK]
      Common Mistakes:
      • Expecting Git to auto-detect project identities
      • Setting only local config and ignoring global
      • Using environment variables instead of config