.gitconfig file structure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the user name in the .gitconfig file.

Git

[user]
	name = [1]

Drag options to blanks, or click blank then click option'

Auser.name

BJohn Doe

Cusername

Dname.user

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'user.name' instead of the actual name.

Confusing the key and value positions.

The name field under the [user] section sets the user's full name in the .gitconfig file.

2fill in blank

medium

Complete the code to set the user email in the .gitconfig file.

Git

[user]
	email = [1]

Drag options to blanks, or click blank then click option'

Auser.email

Bjohn@domain

Cemail.user

[e-mail]

Attempts:

3 left

💡 Hint

Common Mistakes

Using a key name instead of an email address.

Leaving out the domain part of the email.

The email field under the [user] section sets the user's email address in the .gitconfig file.

3fill in blank

hard

Fix the error in the .gitconfig snippet to correctly set the default editor.

Git

[core]
	editor = [1]

Drag options to blanks, or click blank then click option'

Avim

Beditor

Cdefault

Dedit

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic words like 'edit' or 'default' instead of an editor name.

Confusing the key and value.

The editor key under the [core] section sets the default text editor for Git commands. Common editors include 'vim', 'nano', or 'code'.

4fill in blank

hard

Fill both blanks to configure Git to use the credential helper cache with a timeout.

Git

[credential]
	helper = [1] --timeout=[2]

Drag options to blanks, or click blank then click option'

Acache

B3600

Cstore

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'store' instead of 'cache' for temporary storage.

Setting timeout to a non-numeric value.

The helper key under [credential] should be set to cache --timeout=3600. This uses the cache helper which stores credentials temporarily for 3600 seconds (1 hour).

5fill in blank

hard

Fill all three blanks to create an alias for 'git status' as 'st' in the .gitconfig file.

Git

[alias]
	[1] = [2] [3]

Drag options to blanks, or click blank then click option'

Ast

Bstatus

C--short

Dcommit

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'commit' instead of 'status' for the alias.

Omitting the '--short' option for concise output.

The [alias] section lets you create shortcuts. Here, 'st' is an alias for 'git status --short' which shows a brief status output.

Practice

1. What is the main structure used in a .gitconfig file to organize settings?

easy

A. XML tags with attributes

B. Plain text without any structure

C. Sections with key-value pairs

D. JSON objects and arrays

Solution

1. Step 1: Understand the .gitconfig format

   The .gitconfig file organizes settings into sections, each marked by square brackets, like [user].

2. Step 2: Recognize key-value pairs inside sections

   Within each section, settings are written as key = value pairs, for example, name = John.

3. Final Answer:

   Sections with key-value pairs -> Option C

4. Quick Check:

   .gitconfig uses sections and key-value pairs [OK]

Hint: Look for [section] headers and key = value lines [OK]

Common Mistakes:

• Thinking .gitconfig uses JSON or XML
• Assuming it's just plain text without structure
• Confusing it with other config file formats

2. Which of the following is the correct syntax to set the user email in a .gitconfig file?

easy

A. [user]
email = [e-mail]

B. [user]
email: [e-mail]

C. user.email = [e-mail]

D. { "user": { "email": "[e-mail]" } }

Solution

1. Step 1: Identify section and key-value syntax

   In .gitconfig, sections are in square brackets, and keys are assigned values with an equals sign.

2. Step 2: Check each option's syntax

   [user] email = [e-mail] correctly uses [user] section and email = [e-mail] format. [user] email: [e-mail] uses colon instead of equals, which is invalid. user.email = [e-mail] lacks section brackets. { "user": { "email": "[e-mail]" } } is JSON, not valid here.

3. Final Answer:

   [user] email = [e-mail] -> Option A

4. Quick Check:

   Use [section] and key = value syntax [OK]

Hint: Use equals sign (=) inside [section] blocks [OK]

Common Mistakes:

• Using colon (:) instead of equals (=)
• Omitting section headers
• Writing JSON instead of .gitconfig format

3. Given this .gitconfig snippet:

[alias]
  co = checkout
  br = branch
[user]
  name = Alice
  email = [e-mail]

What will be the output of git config --get alias.co?

medium

A. checkout

B. co

C. alias.co

D. Error: key not found

Solution

1. Step 1: Understand alias section usage

   The alias section defines shortcuts for git commands. Here, co is set to checkout.

2. Step 2: Interpret git config --get alias.co

   This command fetches the value of alias.co, which is 'checkout'.

3. Final Answer:

   checkout -> Option A

4. Quick Check:

   alias.co = checkout [OK]

Hint: Aliases map short names to commands, check their values [OK]

Common Mistakes:

• Expecting the key name instead of its value
• Confusing alias names with actual commands
• Assuming error if alias exists

4. Identify the error in this .gitconfig snippet:

[core]
  editor nano
[user]
  name = Bob

medium

A. User name should be in quotes

B. Missing equals sign (=) after editor

C. Section name 'core' is invalid

D. Indentation is not allowed

Solution

1. Step 1: Check key-value syntax in core section

   The line 'editor nano' lacks an equals sign; it should be 'editor = nano'.

2. Step 2: Verify other parts

   The section name 'core' is valid, user name does not require quotes, and indentation is allowed for readability.

3. Final Answer:

   Missing equals sign (=) after editor -> Option B

4. Quick Check:

   Key-value pairs need '=' between key and value [OK]

Hint: Every setting line needs key = value format [OK]

Common Mistakes:

• Forgetting the equals sign
• Thinking quotes are mandatory for strings
• Believing indentation breaks config

5. You want to add a global alias in your .gitconfig to make git st run git status. Which snippet correctly adds this alias globally?

hard

A. [alias]
st = git status

B. [alias]
st: status

C. alias.st = status

D. [alias]
st = status

Solution

1. Step 1: Understand alias syntax in .gitconfig

   Aliases are defined under [alias] section with key = command without 'git' prefix.

2. Step 2: Evaluate each option

   [alias] st = status correctly sets 'st = status'. [alias] st: status uses colon instead of equals. alias.st = status uses invalid syntax without section. [alias] st = git status incorrectly includes 'git' in command.

3. Final Answer:

   [alias] st = status -> Option D

4. Quick Check:

   Alias commands omit 'git' and use key = value [OK]

Hint: Alias commands omit 'git' and use equals sign [OK]

Common Mistakes:

• Including 'git' in alias command
• Using colon instead of equals
• Writing alias outside [alias] section