Repository navigation
Cloning a fork with SSH results in upstream with HTTPS protocol #736
Description
Describe the bug
When cloning a fork, upstream protocol should match origin.
Steps to reproduce the behavior
If I forked this repo:
gh repo clone [email protected]:bendavies/cli.git
Expected vs actual behavior
Actual:
git remote -v
origin [email protected]:bendavies/cli.git (fetch)
origin [email protected]:bendavies/cli.git (push)
upstream https://github.com/cli/cli.git (fetch)
upstream https://github.com/cli/cli.git (push)Expected:
git remote -v
origin [email protected]:bendavies/cli.git (fetch)
origin [email protected]:bendavies/cli.git (push)
upstream [email protected]:cli/cli.git (fetch)
upstream [email protected]:cli/cli.git (push)
Activity
[-]When cloning a fork, upstream protocol should match orogin.[/-][+]When cloning a fork, upstream protocol should match origin.[/+]mislav commentedon Apr 3, 2020
Hi thank you for reporting! This is related to the feature we are planning in #546, but I agree with this being labeled "bug" because SSH mode should have been inferred from your clone argument even if there wasn't a configuration option. 👍
[-]When cloning a fork, upstream protocol should match origin.[/-][+]Cloning a fork with SSH results in upstream with HTTPS protocol[/+]vilmibm commentedon May 13, 2020
gh repo clonenow respects thegit_protocolsetting, so I'm gonna close this.