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.