git commit with message - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this git commit command?

You run the command git commit -m "Initial commit" after staging some files. What will git display?

Git

git commit -m "Initial commit"

A nothing to commit, working tree clean

B

[master (root-commit) abc1234] Initial commit
 3 files changed, 15 insertions(+)

C fatal: no changes added to commit

D error: commit message required

💡 Hint

Think about what happens when you commit after staging files.

When you run git commit -m "message" after staging files, git creates a new commit with that message and shows a summary of changes.

💻 Command Output

intermediate

What error does this git commit command produce?

You run git commit -m without providing a message. What error message will git show?

Git

git commit -m

A error: switch `m' requires a value

B fatal: no commit message

C error: missing commit message after -m

D nothing to commit, working tree clean

💡 Hint

The -m option expects a message string immediately after it.

Git requires a message after -m. Without it, git shows: error: switch `m' requires a value.

🔀 Workflow

advanced

Which command sequence correctly commits changes with a message?

You have modified files and want to commit them with the message "Update README". Which sequence is correct?

A

git add .
git commit -m "Update README"

B

git commit
git add .
git commit -m "Update README"

C

git commit -m "Update README"
git add .

D

git add .
git commit

💡 Hint

Remember you must stage files before committing.

You must add files first with git add, then commit with git commit -m. Option A follows this order.

❓ Troubleshoot

advanced

Why does this git commit command fail?

You run git commit -m "Fix bug" but get the message: fatal: no changes added to commit. Why?

Git

git commit -m "Fix bug"

A The repository is corrupted

B The commit message is too short

C No files were staged before committing

D The branch is not checked out

💡 Hint

Check if you used git add before committing.

Git requires files to be staged before committing. Without staging, it shows: fatal: no changes added to commit.

✅ Best Practice

expert

Which git commit command correctly includes a multi-line message?

You want to commit with a title and a detailed description. Which command correctly does this?

A git commit -m "Fix bug"; git commit -m "This fixes the issue with login timeout."

B

git commit -m "Fix bug
This fixes the issue with login timeout."

C git commit -m "Fix bug" --message "This fixes the issue with login timeout."

D git commit -m "Fix bug" -m "This fixes the issue with login timeout."

💡 Hint

Git allows multiple -m options for multi-line messages.

Using multiple -m options adds multiple paragraphs to the commit message. Option D is correct.

Practice

1. What does the command git commit -m "Update README" do?

easy

A. Saves your changes with the message 'Update README'.

B. Deletes the README file from the repository.

C. Shows the commit history with the message 'Update README'.

D. Creates a new branch named 'Update README'.

Solution

1. Step 1: Understand the git commit command

   The git commit command saves changes to the local repository.

2. Step 2: Understand the -m option

   The -m option adds a message describing the changes.

3. Final Answer:

   Saves your changes with the message 'Update README'. -> Option A

4. Quick Check:

   git commit -m "message" saves changes with message [OK]

Hint: Remember: -m adds your commit message directly [OK]

Common Mistakes:

• Thinking commit deletes files
• Confusing commit with branch creation
• Assuming commit shows history

2. Which of the following is the correct syntax to commit changes with a message in git?

easy

A. git commit -message "Fix bug"

B. git commit --msg "Fix bug"

C. git commit -m "Fix bug"

D. git commit message "Fix bug"

Solution

1. Step 1: Recall the correct flag for commit message

   The correct flag to add a message is -m.

2. Step 2: Check each option's syntax

   Only git commit -m "Fix bug" uses the correct flag and syntax.

3. Final Answer:

   git commit -m "Fix bug" -> Option C

4. Quick Check:

   Use -m for commit message [OK]

Hint: Use -m followed by quotes for commit messages [OK]

Common Mistakes:

• Using -message instead of -m
• Omitting quotes around the message
• Using --msg which is invalid

3. What will be the output of the following commands?

git add file.txt
git commit -m "Add file.txt"

medium

A. Error: No files added to commit.

B. A new branch named 'Add file.txt' is created.

C. file.txt is deleted from the repository.

D. Changes in file.txt are saved with message 'Add file.txt'.

Solution

1. Step 1: Understand git add

   The git add file.txt command stages the file for commit.

2. Step 2: Understand git commit with message

   The git commit -m "Add file.txt" saves the staged changes with the message.

3. Final Answer:

   Changes in file.txt are saved with message 'Add file.txt'. -> Option D

4. Quick Check:

   git add + git commit -m saves changes [OK]

Hint: Add files before commit to save changes [OK]

Common Mistakes:

• Committing without adding files first
• Expecting commit to delete files
• Confusing commit with branch creation

4. You run git commit -m Fix typo but get an error. What is the problem?

medium

A. The commit message must be in quotes.

B. The -m flag is missing.

C. You need to add files before committing.

D. The message 'Fix typo' is too short.

Solution

1. Step 1: Check the commit message syntax

   Commit messages with spaces must be enclosed in quotes.

2. Step 2: Identify the error cause

   Without quotes, git treats 'Fix' as the message and 'typo' as an invalid argument.

3. Final Answer:

   The commit message must be in quotes. -> Option A

4. Quick Check:

   Use quotes around multi-word messages [OK]

Hint: Always quote multi-word commit messages [OK]

Common Mistakes:

• Omitting quotes around messages with spaces
• Forgetting to stage files before commit
• Assuming message length causes errors

5. You want to commit multiple changes with clear messages for each step. Which practice is best?

hard

A. Commit all changes at once with a single message.

B. Commit often with small changes and clear messages using git commit -m.

C. Avoid commit messages to save time.

D. Use git commit without messages and add them later.

Solution

1. Step 1: Understand commit best practices

   Committing often with small, clear messages helps track changes better.

2. Step 2: Evaluate options

   Commit often with small changes and clear messages using git commit -m encourages clear, frequent commits using git commit -m, which is best practice.

3. Final Answer:

   Commit often with small changes and clear messages using git commit -m. -> Option B

4. Quick Check:

   Frequent commits with messages improve tracking [OK]

Hint: Commit small changes often with clear messages [OK]

Common Mistakes:

• Committing too many changes at once
• Skipping commit messages
• Delaying messages until later