Until now we have initiated the repository, added our files into the repository, and confirmed those changes by staging them (pushing them to the staged changes stage) but until they are committed the files are not said to be under version control. (This is because only when you commit does Git record the content of the files and save it as a new phase of that file/files, so that next time it can identify whether the files have any change of content by comparing the existing version to the last saved version).
This is a new addition to your Git lingo: This process is called committing.
So let's make an initial commit of your files. The first time you add a file to the repository and make a commit, Git registers the new file. Any further commits made to these files inside the same repository will be a commit for the changes based on the previous version of the same file available in the repository.
Though Git follows your orders it has a healthy habit of associating...