git commit with message - Step-by-Step Execution

Process Flow - git commit with message

Make changes to files

↓

Stage changes with git add

↓

Run git commit -m "message"

↓

Git creates a new commit with the message

↓

Commit saved in local repository

This flow shows how you save your changes in git with a message describing them.

Execution Sample

Git

git add file.txt
git commit -m "Add file.txt with initial content"

Stages the file.txt and commits it with a message describing the change.

Process Table

Step	Command	Action	Result
1	git add file.txt	Stage file.txt for commit	file.txt is ready to be committed
2	git commit -m "Add file.txt with initial content"	Create commit with message	New commit created with message
3	git log -1	Show last commit message	Commit message: Add file.txt with initial content

💡 Commit created and saved locally with the provided message

Status Tracker

Variable	Start	After git add	After git commit
Staged files	none	file.txt	none (staged cleared after commit)
Last commit message	none	none	Add file.txt with initial content

Key Moments - 2 Insights

Why do I need to use git add before git commit?

git add tells git which changes to include in the commit. Without it, git commit has nothing to save. See execution_table step 1 and 2.

What happens if I forget the -m message in git commit?

Git will open a text editor to type the commit message manually. Using -m lets you add the message directly in the command. See execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the staged file after step 1?

A file.txt

B none

C Add file.txt with initial content

D git commit

💡 Hint

Check the 'Action' and 'Result' columns in step 1 of the execution_table

At which step is the commit message created?

A Step 1

B Step 3

C Step 2

D After all steps

💡 Hint

Look at the 'Command' and 'Result' columns in the execution_table

If you skip git add, what will happen when you run git commit -m "msg"?

A Commit will include all changes automatically

B Commit will fail or create empty commit

C Git will stage files for you

D Git will delete changes

💡 Hint

Refer to key_moments about why git add is needed before commit

Concept Snapshot

git commit -m "message" saves staged changes with a message.
Use git add to stage files first.
Commit message describes the change.
Without -m, git opens editor for message.
Commit is saved locally until pushed.

Full Transcript

To save your changes in git, first stage the files using git add. Then run git commit with the -m option followed by a message in quotes. This message describes what you changed. Git creates a new commit with these staged changes and the message. The commit is saved in your local repository. If you forget to stage files, the commit will have no changes. If you omit the -m message, git opens an editor to type it manually.

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