Committing changes in Git is the process of saving a snapshot of your project's current state to the repository's history. This is done using the git commit command. A commit includes a message that describes the changes, making it easier to track the history of your project. Below are the steps to commit changes in Git, along with sample commands and explanations.

Committing Changes Using git commit

To commit changes, you first need to stage them using the git add command. Once the changes are staged, you can commit them with the git commit command.

Staging Changes

Before committing, you need to stage the changes you want to include in the commit. 

    
# Stage a file for commit
git add file.txt

# Stage all changes in the working directory
git add .

Committing Staged Changes

Once the changes are staged, you can commit them using the git commit command. The -m option allows you to include a commit message directly in the command. 

    
# Commit the staged changes with a message
git commit -m "Added new features and fixed bugs"

# Output example:
# [main abc123] Added new features and fixed bugs
# 3 files changed, 10 insertions(+), 2 deletions(-)

Writing a Good Commit Message

A good commit message is concise and descriptive. It should explain what changes were made and why. Here are some tips for writing effective commit messages:

  • Use the imperative mood (e.g., "Add feature" instead of "Added feature").
  • Keep the first line short (50 characters or less).
  • Provide additional details in the body of the message if necessary.
    
# Example of a good commit message
git commit -m "Add login feature

This commit adds a new login feature to the application. The feature includes user authentication and session management."

Amending a Commit

If you need to make changes to the most recent commit (e.g., to fix a typo in the commit message or add forgotten files), you can use the --amend option. 

    
# Stage additional changes
git add another-file.txt

# Amend the previous commit
git commit --amend -m "Added new features, fixed bugs, and included another-file.txt"

# Output example:
# [main abc123] Added new features, fixed bugs, and included another-file.txt
# 4 files changed, 12 insertions(+), 2 deletions(-)

Committing Without Staging

If you want to commit all changes in the working directory without explicitly staging them, you can use the -a option with the git commit command. 

    
# Commit all changes in the working directory
git commit -a -m "Updated project documentation"

# Output example:
# [main def456] Updated project documentation
# 2 files changed, 5 insertions(+), 3 deletions(-)

Conclusion

Committing changes in Git is a fundamental process that allows you to save snapshots of your project's state. By using the git commit command, you can record changes with descriptive messages, making it easier to track the history of your project. Understanding how to stage, commit, and amend changes is essential for effective version control and collaboration in Git.