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.