The first steps in Git hare the harder ones — we’ve all been through this!. The harder part is probably coming to terms with Git’s technical terminology (pun intended) and being able to express problems using the correct terminology. Again, don’t worry, daily practice will overcome this very soon.
In Git and GitHub terminology, cloning refers to using Git to create a local copy of a repository residing on a remote machine/server (simply stated, downloading a repository using Git). So probably you’ve done that in reversed order, i.e. cloned from
/desktop/‘Remote Team Work to
.c:/…'Linux Command Trial/‘CodeCademy Github Practice’, assuming the former is a server and the latter a local directory. Unless you’ve only copied a repository folder from the remote desktop to your local drive, which doesn’t qualify as cloning, even though you’ve effectively obtained a full (and working) copy of the repository.
I’m not quite sure about this, if your local clone of the repository was even with the GitHub repository, then after fetching there should be no new files to merge (unless a considerable amount of time passed between the two operations, during which the remote repository was updated).
Editing files is not enough, you also need to stage and commit your changes for them to become effective in your repository; only after doing this you are able to push them to the remote repository.
For your initial steps in Git, it’s important that you learn the details of the working area vs the staging area, and about the Index. Here are some links to useful articles:
Also, consider that GitHub offers free interactive tutorials to learn Git by doing things, which you can find at GitHub’s Learning Lab: