Git push ssh失败，使用远程URL而不是原始名称--（错误：未找到存储库）

Question

Hi I have setup Git/Github with SSH successfully. I know this because I went through the Github help guide to check this and all results passed OK.

I can push to my Github repo using the following command for a tag example:

git push origin <tagname>

However, when I try to do the same thing but specify the remote by url, it fails telling me that the repo does not exist:

git push git@github.com:<organisationname>/<reporname>.git <tagname>

I get the following error:

ERROR: Repository not found. fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.

The documentation for git push does support both syntax so I'm stumped as to why the URL version fails and the "origin" version does not?

Answer 1

I found the issue and it was actually a simple one. The user configured for the release plugin was different to the user configured for access to the repos. In my question I have an example including "git" as the user, which actually did not represent the URL used by the maven plugin, it was using a different user.

So for clarity, if ssh access was based on "user1" and maven release plugin was configured to run with "user2" then that's when I get the failed push.

To handle this in a user ambiguous way the git docs suggests always pushing using the "git" user.

For example, even with an ssh key setup for "user1", in my setup the following push was still successful:

git push git@github.com:<organisationname>/<reporname>.git <tagname>

But the following is not:

git push user2@github.com:<organisationname>/<reporname>.git <tagname>

Now I know the reason, its pretty obvious and feels silly that I missed that in my config originally. This also explains why the original question if run on any repo setup with proper ssh keys works fine, as the comments suggest.