Why configuration improves workflow in Git - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use a .git/config file in your project?

What is the main benefit of having a .git/config file in your project directory?

A It deletes all untracked files when you run Git commands.

B It automatically commits changes without user input.

C It allows you to set project-specific Git settings that override global settings.

D It disables Git hooks for the project.

💡 Hint

Think about how configuration files help customize behavior for each project.

A .git/config file in a project folder lets you set Git options that apply only to that project, improving workflow by tailoring Git behavior without changing global settings.

💻 Command Output

intermediate

Effect of git config --local user.email

What will be the output of git config --get user.email after running git config --local user.email "[e-mail]" inside a Git repository?

Git

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

A The global user.email value

B No output, command fails

C An error message about missing repository

D [e-mail]

💡 Hint

Local config overrides global config inside a repository.

Setting user.email with --local changes it only for the current repository. The git config --get command then shows this local value.

🔀 Workflow

advanced

How does .gitattributes improve collaboration?

Which of the following best explains how a .gitattributes file improves team workflow?

A It tracks file changes outside the Git repository.

B It enforces consistent handling of line endings and file types across all team members.

C It disables pushing to the main branch.

D It automatically merges all conflicts without user input.

💡 Hint

Think about how different computers handle text files differently.

.gitattributes helps avoid problems by telling Git how to treat files, like normalizing line endings, so everyone on the team sees the same content and avoids merge conflicts.

❓ Troubleshoot

advanced

Why does git ignore not work as expected?

You added a pattern to your .gitignore file, but Git still tracks those files. What is the most likely reason?

A The files were already tracked by Git before adding to <code>.gitignore</code>.

B The <code>.gitignore</code> file is missing a newline at the end.

C Git does not support ignoring files with <code>.gitignore</code>.

D The files are too large to be ignored.

💡 Hint

Think about when Git starts tracking files.

Git only ignores untracked files matching .gitignore. If files were already added to Git, they remain tracked until removed explicitly.

✅ Best Practice

expert

Why commit hooks improve workflow reliability?

How do Git commit hooks configured in .git/hooks improve workflow reliability?

A They automatically check code quality or run tests before allowing commits.

B They speed up the commit process by skipping validations.

C They delete all uncommitted changes after each commit.

D They prevent pushing to remote repositories.

💡 Hint

Think about how automation can prevent mistakes before saving work.

Commit hooks run scripts before commits to ensure code meets standards or tests pass, reducing errors and improving team workflow.

Practice

1. Why is configuring Git settings important for a team working on the same project?

easy

A. It automatically writes commit messages for all team members.

B. It makes Git run faster on all computers automatically.

C. It deletes old branches to keep the repository clean.

D. It ensures everyone uses the same settings, avoiding conflicts and mistakes.

Solution

1. Step 1: Understand team consistency needs

   When a team shares a project, using the same Git settings helps avoid conflicts and mistakes.

2. Step 2: Recognize configuration role

   Git configuration sets rules like user name, email, and merge behavior that everyone follows.

3. Final Answer:

   It ensures everyone uses the same settings, avoiding conflicts and mistakes. -> Option D

4. Quick Check:

   Team consistency = It ensures everyone uses the same settings, avoiding conflicts and mistakes. [OK]

Hint: Think about teamwork and shared rules for smooth collaboration [OK]

Common Mistakes:

• Confusing configuration with performance improvements
• Assuming config deletes branches automatically
• Believing config writes commit messages

2. Which of the following is the correct syntax to set your Git user email globally?

easy

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

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

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

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

Solution

1. Step 1: Recall Git config command structure

   The correct command uses 'git config' followed by '--global' and the key-value pair.

2. Step 2: Identify correct option

   git config --global user.email "[e-mail]" matches the correct syntax: git config --global user.email "[e-mail]".

3. Final Answer:

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

4. Quick Check:

   Correct git config syntax = git config --global user.email "[e-mail]" [OK]

Hint: Remember: 'git config --global key value' is the pattern [OK]

Common Mistakes:

• Using 'git set' instead of 'git config'
• Placing --global after the key
• Mixing order of commands

3. What will be the output of the command git config --list after setting user.name and user.email globally?

medium

A. Lists all Git configuration settings including user.name and user.email

B. Shows only the user.name setting

C. Displays an error if user.email is not set locally

D. Deletes all local Git configurations

Solution

1. Step 1: Understand git config --list behavior

   This command shows all current Git settings from global, system, and local configs combined.

2. Step 2: Confirm presence of user.name and user.email

   Since both are set globally, they appear in the list output.

3. Final Answer:

   Lists all Git configuration settings including user.name and user.email -> Option A

4. Quick Check:

   git config --list shows all settings = Lists all Git configuration settings including user.name and user.email [OK]

Hint: Think of it as a full list of your Git settings [OK]

Common Mistakes:

• Assuming it shows only local settings
• Expecting an error if local config missing
• Confusing it with a delete command

4. You tried to set your Git username with git config user.name John Doe but it didn't work as expected. What is the likely problem?

medium

A. The command should be git set user.name "John Doe".

B. You must use --global flag to set user.name.

C. You forgot to add quotes around the name with spaces.

D. Git does not allow spaces in user.name.

Solution

1. Step 1: Identify issue with spaces in command

   Git treats each space-separated word as a separate argument, so 'John Doe' without quotes breaks the command.

2. Step 2: Correct usage with quotes

   Using quotes like "John Doe" groups the full name as one value.

3. Final Answer:

   You forgot to add quotes around the name with spaces. -> Option C

4. Quick Check:

   Quotes needed for multi-word values = You forgot to add quotes around the name with spaces. [OK]

Hint: Use quotes when values have spaces [OK]

Common Mistakes:

• Thinking --global is always required
• Using 'git set' instead of 'git config'
• Believing spaces are not allowed at all

5. A team wants to ensure all commits have a signed-off message automatically. Which Git configuration helps enforce this workflow?

hard

A. Use alias.commit to add sign-off manually each time.

B. Configure format.signoff to true for automatic signed-off-by messages.

C. Set commit.template to a file with the sign-off message.

D. Set push.default to 'signed' to enforce sign-offs.

Solution

1. Step 1: Understand signed-off-by messages

   Signed-off-by messages certify contributions and can be added automatically via configuration.

2. Step 2: Identify config for automatic sign-off

   Setting format.signoff to true makes Git automatically append the Signed-off-by line to commit messages.

3. Step 3: Evaluate other options

   commit.gpgsign is for cryptographic signing; commit.template pre-fills but doesn't enforce automatically; push.default does not control sign-offs.

4. Final Answer:

   Configure format.signoff to true for automatic signed-off-by messages. -> Option B

5. Quick Check:

   Automatic signed-off-by = Configure format.signoff to true for automatic signed-off-by messages. [OK]

Hint: format.signoff=true enables automatic signed-off-by messages [OK]

Common Mistakes:

• Confusing signed-off-by message with GPG signing (commit.gpgsign)
• Using alias instead of config for automation
• Misunderstanding push.default role
• Thinking commit.template enforces automatically