fatal: 'origin' does not appear to be a git repository

后端 未结 6 1075
情深已故
情深已故 2020-12-22 18:26

I\'ve a repository moodle on my Github account which I forked from the official repository.

I then cloned it on my local machine. It worked

6条回答
  •  北荒
    北荒 (楼主)
    2020-12-22 19:09

    This does not answer your question, but I faced a similar error message but due to a different reason. Allow me to make my post for the sake of information collection.

    I have a git repo on a network drive. Let's call this network drive RAID. I cloned this repo on my local machine (LOCAL) and on my number crunching cluster (CRUNCHER). For convenience I mounted the user directory of my account on CRUNCHER on my local machine. So, I can manipulate files on CRUNCHER without the need to do the work in an SSH terminal.

    Today, I was modifying files in the repo on CRUNCHER via my local machine. At some point I decided to commit the files, so a did a commit. Adding the modified files and doing the commit worked as I expected, but when I called git push I got an error message similar to the one posted in the question.

    The reason was, that I called push from within the repo on CRUNCHER on LOCAL. So, all paths in the config file were plain wrong.

    When I realized my fault, I logged onto CRUNCHER via Terminal and was able to push the commit.

    Feel free to comment if my explanation can't be understood, or you find my post superfluous.

提交回复
热议问题