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

Convert conventially cloned repostiory #235

Open
nomeata opened this issue Nov 10, 2017 · 4 comments · May be fixed by #293
Open

Convert conventially cloned repostiory #235

nomeata opened this issue Nov 10, 2017 · 4 comments · May be fixed by #293

Comments

@nomeata
Copy link

nomeata commented Nov 10, 2017

It is very convenient to use

git clone [email protected]:upstream/repo

and start hacking, only to later regret that I should have used

 git hub clone  -t upstrema/repo

instead. Or maybe I have had cloned these repositories before starting to use git-hub.

It would be great if

git hub clone -t

in an already-cloned repository would

  • Figure out the upstream repository based on git remote.
  • Create a clone on GitHub
  • Set up the fork remote accordingly, if -t is specified.
@nomeata
Copy link
Author

nomeata commented Nov 10, 2017

This is related to #158, which asks for converting a git-hub-created repository into a triangular one. My request goes a bit further in that it starts with a non-git-hub-aware repository.

@joshtriplett
Copy link

I'd love to have this as well; I regularly encounter this situation, when I started out cloning a repository to experiment with it and then later wanting to contribute to it.

@nomeata
Copy link
Author

nomeata commented Aug 31, 2018

I think it is possible to do this manually (clone on github, add the git remote, set the hub.upstream and hub.forkremote git configs). But automation would be better :-)

@joshtriplett
Copy link

@nomeata It's certainly possible, just tedious and error-prone.

@llucax llucax modified the milestones: Future, v2.2.0 Feb 14, 2021
@llucax llucax modified the milestones: v2.2.0, Future Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants