Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong remote is set if GitHub user already has a repo named "opam-repository" #118

Open
leviroth opened this issue Dec 13, 2020 · 0 comments
Labels

Comments

@leviroth
Copy link

I ran opam publish for the first time yesterday. It forked opam-repository for me and tried to set up my fork as a remote for the local clone of https://github.com/ocaml/opam-repository.

However, I already have a repo named "opam-repository": https://github.com/leviroth/opam-repository, so my new fork ended up being named "opam-repository-1": https://github.com/leviroth/opam-repository-1

opam publish did $ git remote add user git@github.com:leviroth/opam-repository.git, so the changes ended up getting pushed to the wrong repo: https://github.com/leviroth/opam-repository/tree/opam-publish-reddit_api_async-reddit_api_kernel.0.1.0

Workaround

I changed the remote to point to the right repo and opam publish then worked fine:

$ git remote remove user
$ git remote add user git@github.com:leviroth/opam-repository-1.git
@rjbou rjbou added the bug label Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants