Discover the secret to tracking every change in your code with these 5 Git commit examples

Table of content

  1. Introduction
  2. What is Git and why is it important?
  3. The basics of Git commit
  4. Five Git commit examples
  5. Example 1: Initial commit
  6. Example 2: Committing changes to a file
  7. Example 3: Creating a new branch
  8. Example 4: Merging branches
  9. Example 5: Reverting to a previous commit
  10. Conclusion


Git is a version control system that allows developers to track and manage changes to their code over time. It is an essential tool for software development, especially when working on large projects with multiple team members. One of the key features of Git is the ability to make commits, which are essentially snapshots of your code at a particular point in time.

In this article, we will explore the concept of Git commits and how they can be used to track changes in your code. We will provide examples of different types of commits and explain why they are important. By the end of this article, you should have a solid understanding of how to use Git commits effectively in your own development projects. So, let's get started!

What is Git and why is it important?

Git is a distributed version control system used in software development to keep track of changes made to code. It allows multiple developers to work on the same codebase simultaneously and keeps track of all the changes that are made. Git operates by creating a repository, which is a collection of all the code, along with information about the changes made to it.

Git is an essential tool for developers working on any project, including Android applications. Here are a few reasons why Git is important:

  • Collaboration: Git allows multiple developers to work on the same codebase without interfering with each other's work. Each developer can create a branch to work on a specific feature or bug fix and then merge it back into the main codebase once it's complete.

  • Version control: Git keeps track of changes made to the codebase, which allows developers to revert to a previous version if needed. It also helps developers debug issues by providing a history of changes that were made to the codebase.

  • Backup: Git makes it easy to create backups of the codebase by creating copies of the repository. This ensures that even if something happens to the local copy of the code, there is always a backup available.

  • Community: Git is used by millions of developers all over the world, which means there is a large community available to answer questions and provide support.

Overall, Git is an essential tool for developers that enables collaboration, version control, backups, and community support.

The basics of Git commit

Git commit is an essential part of version control in Android application development. It allows developers to track changes to their code and collaborate with other team members. Here are some basics to help you understand Git commit:

What is Git commit?

Git commit is a command used in version control systems like Git to create a snapshot of the changes made to the codebase. This snapshot contains information about what changes were made, who made them, and when they were made.

How does Git commit work?

When you make changes to your codebase, such as adding new files or modifying existing ones, you use Git to add these changes to the staging area. Once you are happy with the changes in the staging area, you use Git commit to create a snapshot of these changes.

What is included in a Git commit?

A Git commit typically includes the following information:

  • A unique identifier called a commit ID
  • The author of the commit
  • The date and time the commit was made
  • A commit message describing the changes made

Why is Git commit important?

Git commit is important for several reasons:

  • It allows developers to track changes to their code over time, making it easier to debug issues and roll back changes if necessary.
  • It enables collaboration between team members by providing a centralized location for all changes to be stored.
  • It encourages good coding practices by promoting frequent commits and detailed commit messages.

Tips for using Git commit

Here are some tips for using Git commit effectively:

  • Commit early and often to avoid losing changes and to make it easier to roll back if needed.
  • Use descriptive and concise commit messages that explain what changes were made and why.
  • Use branching to work on new features or bug fixes without impacting the main codebase until they are ready to be merged.

    Five Git commit examples

When working on an Android app, tracking every change made in the code is crucial for debugging and collaboration purposes. One of the best tools for this job is Git – a distributed version control system that enables developers to track changes in their code and collaborate with others seamlessly. Here are that will help you better understand how Git works and how to use it effectively.

1. Initial Commit

The initial commit is the first commit you make when starting a new project. This commit sets up the project repository and establishes the base for all future development. To make an initial commit, follow these steps:

  • Initialize a Git repository in your project folder by running git init.
  • Stage all files in the folder by running git add ..
  • Make the commit by running git commit -m "Initial commit".

2. Adding New Features

As you continue developing your Android app, you will need to add new features and functionality. To add new code changes to your Git repository, follow these steps:

  • Stage the changes you made using git add filename or git add . to add all files and directories.
  • Commit the changes with a descriptive message using git commit -m "Added new feature XYZ".

3. Fixing Bugs

Bugs are an inevitable part of software development, and tracking and fixing them is essential. Here's how you can use Git to fix bugs in your code:

  • Identify the bug in your code.
  • Make the necessary changes to the code.
  • Stage the changes using git add filename or git add ..
  • Commit the changes with a descriptive message using git commit -m "Fixed bug ABC".

4. Reverting Changes

Sometimes, you might make a change to your code that doesn't work as intended, and you need to revert it. Here's how you can use Git to undo a previous commit:

  • Identify the commit you want to revert to by running git log.
  • Use the git revert command followed by the commit hash to undo the changes.

5. Merging Changes

When collaborating on a project, multiple developers may be working on the same code. Git makes it easy to merge changes from different developers into a single codebase. Follow these steps to merge changes:

  • Create a new branch from the master branch by running git branch new_branch_name.
  • Switch to the new branch by running git checkout new_branch_name.
  • Make changes to the code and commit them.
  • Switch back to the master branch by running git checkout master.
  • Merge the changes from the new branch using git merge new_branch_name.

In conclusion, Git is an essential tool for Android app development because it enables developers to track and collaborate on code changes effectively. By following these , you can use Git to streamline your development processes and ensure that you always have an accurate record of your code changes.

Example 1: Initial commit

A Git commit is essentially a snapshot of your code at a specific point in time. The first commit you make in a project is known as the initial commit. Here are some key things you need to know about the initial commit:

  • An initial commit is created with the command: git commit -m "Initial commit"
  • It captures the state of the codebase at the very beginning of the project.
  • It marks the start of a Git repository, which is a central location for your code and a record of all changes you make to it.
  • An initial commit sets the baseline for all future changes to the codebase. This makes it easier to track and manage updates.

Creating an initial commit is a crucial first step in any new project. When you create an initial commit, you are establishing a foundation for your work and setting up a system for tracking changes as the project evolves. It's important to give careful consideration to the messages you include with your commit, as these messages become part of the permanent record of the project. By creating a comprehensive initial commit, you make it easier for yourself and others to understand the evolution of the codebase and to collaborate effectively on the project.

Example 2: Committing changes to a file

Whenever you make changes to your code, you need to track those changes with a Git commit. This ensures that you can easily revert to previous versions of your code if necessary, and that your code is properly documented throughout its development cycle. Here's an example of how to commit changes to a file in Git:

  1. First, make changes to the file in question using your preferred text editor or integrated development environment (IDE).

  2. Once you've made your changes, save the file and return to the command line.

  3. Use the git add command to stage your changes for commit. This tells Git which files you want to include in your next commit. For example, if you've made changes to a file called, you would use the following command:

    git add

    This tells Git to stage the file for commit.

  4. Next, use the git commit command to commit your changes. This creates a new snapshot of your code with the changes you've made. For example:

    git commit -m "Added a new method to"

    This creates a new commit with the message "Added a new method to". The message should be a brief summary of the changes you've made.

  5. Finally, use the git push command to upload your changes to a remote repository if necessary. This is especially important if you're collaborating with others on the same codebase. For example:

    git push origin master

    This command pushes your changes to the master branch of the remote repository named origin.

Committing changes to a file is one of the most common workflows in Git, and it's essential to any software development project. By following these simple steps, you can ensure that changes to your code are properly tracked and documented throughout the development process.

Example 3: Creating a new branch

A branch is a separate line of development that allows you to work on a feature or fix a bug without affecting the main codebase. Creating a new branch is an essential part of Git workflow, and it's easy to do with a few simple steps:

  1. Start by opening up the terminal or the Git Bash window, and navigate to your project directory.
  2. Type in the command git branch to see the list of all the branches in your repository. The output will show you the default branch, which is usually master.
  3. Now use the command git checkout -b followed by the branch name you want to create. For example, if you want to create a new branch called new-feature, the command would look like this git checkout -b new-feature.
  4. Once you execute the command, you will see a message saying that the new branch has been created, and you have been switched to it.
  5. You can now start making changes to the code and commit them to the new branch. Remember, every time you make a commit, it only affects the current branch the repository is pointing to.

Creating a new branch is essential when working on a new feature or fixing a bug. It allows you to keep your main codebase clean and stable while you experiment with new ideas without worrying about breaking the existing code. Once you're finished with your new branch, you can merge it back into the main codebase using a pull request, a topic that we will cover in the next section.

Example 4: Merging branches

When multiple developers are working on the same project, it is necessary to create multiple branches to manage the code base effectively. Once each developer has completed their work on their respective branches, there comes a time when their work needs to be merged with the main branch. In Git, this can be done easily with the merge command.

Here's an example of how two branches can be merged using Git:

  1. Create a new branch: Suppose you have two branches in your repository, master and feature. Create a new branch, new-feature, using the command:

    git branch new-feature
  2. Switch to the new branch: To work on the code in new-feature branch, switch to the branch using the command:

    git checkout new-feature
  3. Make some changes: Make the necessary changes to the code in new-feature branch.

  4. Commit changes: Once you have made the changes, commit the code using the command:

    git commit -a -m "Commit message"
  5. Switch back to the main branch: After committing your changes to new-feature, switch back to the master branch using the command:

    git checkout master
  6. Merge the branches: Finally, merge the new-feature branch to master branch using the command:

    git merge new-feature
  7. Resolve conflicts (if any): Git will automatically merge the code in both branches. However, if any conflicts arise due to changes made in both the branches, Git will ask you to resolve them. Fix the conflicts manually by editing the code and committing the changes again.

Merging branches is an important aspect of collaborative coding in a team. Git makes it easy to merge branches with its simple yet powerful merge command. Always make sure to commit your changes to the branch before switching branches to avoid any discrepancies in the code.

Example 5: Reverting to a previous commit

In Git, it's easy to revert to a previous commit if you need to undo changes that were made. Git has a command specifically for this called "git revert." This command creates a new commit that effectively undoes the changes made by a previous commit. Here's how you can use it:

  1. Identify the commit you want to revert to: Use the "git log" command to display the list of commits in your repository. Make note of the commit ID for the one you want to revert to.

  2. Use the "git revert" command: Type "git revert" followed by the commit ID you want to revert to. This will create a new commit that undoes the changes from the selected commit.

  3. Review your changes: After you've created the new commit, you'll want to review your changes. Use the "git show" command to see the changes made in the new commit.

  4. Push your changes: Once you're satisfied with the changes made in the new commit, push your changes to the remote repository using the "git push" command.

Reverting to a previous commit is a helpful feature in Git, especially when you need to undo changes or errors that were made. With the "git revert" command, you don't have to worry about losing any previous commits, and you can easily get back to a previous state in your project.


Git is a powerful tool that allows developers to track changes to their code and collaborate with others. By using Git commits, developers can easily keep track of changes to their codebase and revert to previous versions if necessary. In this article, we covered five examples of Git commits and how they can be used in Android application development.

  • The initial commit sets up the repository and establishes a baseline for future changes.

  • The feature branch commit creates a new branch and starts work on a new feature.

  • The merge commit combines two branches into one.

  • The hotfix commit addresses a critical issue in the codebase.

  • The refactor commit reorganizes and optimizes code without changing its functionality.

By incorporating these different types of commits into their workflow, developers can streamline their development process and ensure that changes are tracked and managed properly. With Git as their tool of choice, Android developers can rest assured that they have control over their codebase and can easily collaborate with others to build great apps.

Cloud Computing and DevOps Engineering have always been my driving passions, energizing me with enthusiasm and a desire to stay at the forefront of technological innovation. I take great pleasure in innovating and devising workarounds for complex problems. Drawing on over 8 years of professional experience in the IT industry, with a focus on Cloud Computing and DevOps Engineering, I have a track record of success in designing and implementing complex infrastructure projects from diverse perspectives, and devising strategies that have significantly increased revenue. I am currently seeking a challenging position where I can leverage my competencies in a professional manner that maximizes productivity and exceeds expectations.
Posts created 2029

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Begin typing your search term above and press enter to search. Press ESC to cancel.

Back To Top