I was trying this:
mkdir ~/gitremote
cd ~/gitremote
git init --bare
I can see file names like
HEAD config hooks objects
branches description info refs
OK, then in another directory,
git clone trosky@localhost:/Users/trosky/gitremote
vi readme (add one line)
git add .
git commit -m "1st file"
git push origin master
Then it gives an error:
$git push origin master
error: src refspec master does not match any.
error: failed to push some refs to 'trosy@localhost:/Users/trosky/gitremote'
I searched google and it says this kind of error is due to empty folder on remote repo. But the remote repo is not empty, and locally I'm committing a file that's not empty either. Why this error still prompts out?
How to fix it? Thanks.
Try with the syntax:
Since you are pushing to an empty repo, you need to explicitly push
master
.Otherwise, the default
push.policy
beingsimple
, Git would look for a branch namedmaster
in your remote repo (and since your remote bare repo is empty, it has nomaster
branch yet)Of course, you won't see any readme in your remote bare repo, since it is a bare repo: no working tree.
One is using the file protocol also called local protocol, the other ssh protocol. You don't need ssh here.
You can use
git clone /Users/trosky/gitremote
instead.git clone /Users/trosky/gitremote
is used the local protocol. Because your remoterepo is on your local PC, so the local protocol is suitable and fast.git clone 'trosy@localhost:/Users/trosky/gitremote'
is used scp to transfer data which mainly used for different devices data transfer.After you push to remote repo, you may go to the remote repo folder but not find the pushed file. But it’s actually exist. Because bare repo has not working directory. It’s stored in
/Users/trosky/gitremote/objects
. And you can check the commit SHA-1 in/Users/trosky/gitremote/refs/heads/master
is in accordance with local repo.