As jeremyharris, a git documentation site and especially an online book , said, you can speed up the basics.
A few quick notes that may lead you to your original problem.
Command
git clone used to pull a copy (clone) from an existing git repository. By default, it creates a folder in the folder in which you execute it, with the .git folder. The created cloning folder is your working copy, and the .git folder is your local copy of the repository.
git clone is different from most other git commands. All (or most?) Of other git commands require that the command be executed in the working copy folder created by the clone. (The base repositories are slightly different, as they do not have working copies, but this should not apply here.) So, after execution:
$ git clone <remote repo> <repo name>
make:
$ cd <repo name>
to enter the working copy before executing any other commands. Executing commands outside the working folder will result in a not a git repository message.
After making changes to the file, git add <filename> adds it to the index (marked to indicate readiness for commit), and git commit -m '<commit message>' then commits the changes.
source share