Git Commits Part 2

Lecture 112:- Git Commits Part 2

In Git, a commit is a snapshot of the codebase at a particular point in time. When you make changes to your code, you can use the Git command git commit to create a new commit that represents those changes.
 

Each commit has a unique identifier called a SHA-1 hash, which is a 40-character string that represents the contents of the commit. You can use this identifier to refer to the commit in Git commands.

When you create a commit, Git records the changes that you've made to the code, along with some metadata such as the author of the changes, the commit message, and the date and time that the commit was created. The commit message is a brief description of the changes that were made in the commit.

In Git, commits form a linked list, with each commit pointing to its parent commit. This allows you to see the history of changes to the code, and to easily navigate between different versions of the code.

It's good practice to make frequent, small commits that represent logical changes to the code, rather than making one large commit with all your changes. This makes it easier to understand the changes that were made, and to revert to previous versions of the code if needed.