Git push error: "origin does not appear to be a git repository"

I am following the instructions given here to create a Git repository. All went well until the last line:

$ git push -u origin master  

> fatal: 'origin' does not appear to be a git repository
> fatal: The remote end hung up unexpectedly

I'm using git version 1.7.11.3 on OS X 10.6.8

$ git remote -v  

returns nothing

Config file for the repository:

[core]
repositoryformatversion = 0  
filemode = true  
bare = false
logallrefupdates = true  
ignorecase = true  

I've had to open sudoers file using sudo visudo command and add the following to it (under # User privilege specification):

git ALL=(ALL) ALL.  

Now if I do:

$ git remote add origin /Volumes/500GB/git-repository/myproject.git  

it comes back with no error, but I don't see any code in the repository (it has the aforementioned directories like branches, hooks, ...)

If I do:

$ git push -u origin master  
fatal: 'origin' does not appear to be a git repository
fatal: The remote end hung up unexpectedly

$ git remote -v   
origin /Volumes/500GB/git-repository/myproject.git (fetch)     
origin /Volumes/500GB/git-repository/myproject.git (push)

As it has already been mentioned in che's answer about adding the remote part, which I believe you are still missing.

Regarding your edit for adding remote on your local USB drive. First of all you must have a 'bare repository' if you want your repository to be a shared repository i.e. to be able to push/pull/fetch/merge etc..

To create a bare/shared repository, go to your desired location. In your case:

$ cd /Volumes/500gb/   
$ git init --bare myproject.git

See here for more info on creating bare repository

Once you have a bare repository set up in your desired location you can now add it to your working copy as a remote.

$ git remote add origin /Volumes/500gb/myproject.git

And now you can push your changes to your repository

$ git push origin master

Here are the instructions from github:

touch README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/tqisjim/google-oauth.git
git push -u origin master

Here's what actually worked:

touch README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/tqisjim/google-oauth.git
git clone origin master

After cloning, then the push command succeeds by prompting for a username and password

Most likely the remote repository doesn't exist or you have added the wrong one.

You have to first remove the origin and re-add it:

git remote remove origin
git remote add origin https://github.com/username/repository

Your config file does not include any references to "origin" remote. That section looks like this:

[remote "origin"]
    url = git@foo.com:repository.git
    fetch = +refs/heads/*:refs/remotes/origin/*

You need to add the remote using git remote add before you can use it.

When you create a repository in bitbucket.org, it gives you instructions on how to set up your local directory. Chances are, you just forgot to run the code:

git remote add origin https://[email protected]/username/reponame.git

May be you forgot to run "git --bare init" on the remote? That was my problem

I'll still share my short answer humbly, knowing that I'm super late to answer this question.

Here's, a simple and clean explanation that solved my issue

Also, since I was using the SSH key I used the following command:

• $ git remote add origin [email protected]:{your-username}/{your-remote-repo-branch}

for instance it would look like:

• $ git remote add origin [email protected]:aniketrb-github/microservices.git

If you are using the HTTPS URL, refer to the answer provided by @sunny-jim above.

Do correct me if I'm wrong. Thanks.

my case was a little different - unintentionally I have changed owner of git repository (project.git directory in my case), changing owner back to the git user helped

If you are on HTTPS do this-

git remote add origin URL_TO_YOUR_REPO

I had this problem cause i had already origin remote defined locally. So just change "origin" into another name:

git remote add originNew https://github.com/UAwebM...

git push -u originNew

or u can remove your local origin. to check your remote name type:

git remote

to remove remote - log in your clone repository and type:

git remote remove origin(depending on your remote's name)

To resolving this problem.I just create a new folder and put some new files.Then use these commond.

* git add .
* git commit 
* git remote add master `your address`

then it tells me to login in. To input your username and password. after that

git pull 
git push origin master

finished you have pushed your code to your github

Here is how I resolved this issue

Go to the remote repository on Github and copy the project's repository url.

On git bash type: git remote add origin the remote repository url goes here

Setting remote repository URL worked for me:

git remote set-url origin https://github.com/path-to-repo/MyRepo.git

See this is the issue we get because either your repo is not accessible from the CLI or You are not authorized to do that 2nd case is simple you simply request the access then you will able to do that. for the 1st case if git push origin <private_branch_name> is not working then it will give the solution in the CLI itself Just follow with just one step:

1. git remote add <name> <URL> . enter image description here <URL> can be accessed using the UI of Gitlab/Github -> clone -> copy https. link and then
2. git push origin <private_branch name> Now raise the MR. Refer Image.