FR: Automatically add upstream remote to forked repository

[calebdw]

Hello!

Is your feature request related to a problem? Please describe.
I get tired of manually adding the upstream remote for my forked repositories.

Describe the solution you'd like
It would be nice if jj could be configured to automatically detect this via the api (e.g., github/gitlab/etc) and register the remote (the name could be configurable but could default to upstream).

Describe alternatives you've considered
I have a bash script I used to execute when using git. I could adapt this script to jj, but given that configuring the upstream remote is pretty common I think it would be great to add support natively.

Thanks!

[martinvonz]

When do you imagine this would happen?

[calebdw]

Probably right after cloning a new repo, but I suppose there might could also be a remote discover command or something that could be executed on existing repos

[ilyagr]

The github CLI has a gh repo clone command that does that. So, if you are OK with co-located repos, you could do that, and then jj git init --colocated.

An alternative to adding this all to jj would be to fork gh to make it work nicer with jj. I'm not sure we are at the point where they would accept patches for this, but maybe?

(But adding it to jj itself might make sense too, I don't mean to reject that idea. Unfortunately, gh is written in Go, not Rust, so it's not trivial to just link it to jj; we'd have to call the CLI or use the same JSON apis and reimplement gh)

[PhilipMetzger]

I don't like the idea of fetching this information until something jj gitlab/github/gerrit exists.