git commit with message - Commands & Configuration

Introduction

When you make changes to files in a project, you need to save those changes in a history log. The git commit command saves your changes with a short note explaining what you did. This helps you and others understand the history of the project.

After editing files and you want to save a snapshot of your work.

When you want to add a clear explanation of what changes you made.

Before sharing your work with others or pushing to a shared repository.

To keep track of progress in small, understandable steps.

When you want to be able to go back to a previous version if needed.

Commands

This command tells git to include all changed files in the next commit. It prepares your changes to be saved.

Terminal

git add .

Expected Output

No output (command runs silently)

This command saves your prepared changes with the message 'Add user login feature' explaining what you did.

Terminal

git commit -m "Add user login feature"

Expected Output

[main abc1234] Add user login feature

 3 files changed, 45 insertions(+), 2 deletions(-)

→

-m - Allows you to write the commit message directly in the command line.

This command shows the most recent commit in a short format to verify your commit was saved.

Terminal

git log --oneline -1

Expected Output

abc1234 Add user login feature

→

--oneline - Shows each commit in a single line for easy reading.

→

-1 - Limits the output to only the latest commit.

Key Concept

If you remember nothing else from this pattern, remember: git commit -m "message" saves your changes with a clear note explaining what you did.

Common Mistakes

Running git commit without adding files first

No changes are saved because git does not know which files to include.

Always run git add to stage your changes before committing.

Using git commit without the -m flag and message

Git opens an editor which might confuse beginners or cause the commit to be aborted if no message is saved.

Use git commit -m "your message" to write the message directly and avoid confusion.

Summary

Use git add . to prepare all changed files for saving.

Use git commit -m "message" to save changes with a clear explanation.

Use git log --oneline -1 to check your latest commit.

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