Git has an additional stage between the working directory and the repository.
The idea is that you might be working on multiple unrelated things without wanting to commit all changes in one go.
If you have push access to the Monitoring Plugins repository, run the command: This will show a list of changes in the working directory.
Newly made changes appear in red, while changes added to the index are shown in green.
Therefore, the changes that should be committed must first be added to the so-called for changes to existing ones.
When you commit using git commit, only the changes in the index are considered. To share them with others, you have to push them to a remote repository, or have someone pull from your publicly accessible repository (in most cases you will still have to push changes there, unless if you were running a git daemon straight off your working repository).
Each branch and tag refer to an object name (SHA1 hash), and each commits have one or more parents (commit objects).
Although SHA1 hashes are 40 digits long, with Git you only have to type a handful of digits to reference one. This creates your own local repository, and until you want to distribute your change or merge changes from someone else, everything that follows can happen offline.