#3750 Provide SSH clone url even when cloning is disabled
Opened 6 years ago by bex. Modified 6 years ago

I believe a common workflow is

  1. Clone the upstream "base" repository
  2. Fork that repository
  3. Add your clone as a remote for PRs.

This allows master to track the upstream while your repo serves as a source of PRs.

Pagure doesn't support this by hiding ssh urls for an indeterminate period of time.


hiding ssh urls for an indeterminate period of time.

The SSH urls are only hidden up until you can access the git repo (so up until gitolite's config is re-generated).
The idea is not to provide these SSH URLs while you can't do anything with it.

I understand why they are hidden. However, I don't need the url to respond in order to type git remote add origin SSH_URL during my repo set up.

@bkabrda would you like the chime in here?

I'd actually prefer that we keep the SSH URLs hidden until they are useful. Anyone who knows how the system will set up the URLs can pretty easily predict and type it out if they want to, but it's more trouble than it's worth to change this behavior since it confuses people if the URL is available but doesn't work.

I've had several users complain that they get the URL when it's not ready yet and cloning fails, so clearly there are people who want the current way. I think maybe a solution that would work for everyone would be displaying the URL, but making it clear that it's not available for pushing yet, e.g. use a red background for the input box and show a tooltip when user does mouseover?

making it clear that it's not available for pushing yet

There is already a big red banner in the front page of the project so I'm not sure it'd help so much :(

hide it under a toggle?

if we were to show it but make it not-selectable, would that help or not at all?

if we were to show it but make it not-selectable, would that help or not at all?

I'd like to be able to cut and paste it.

Log in to comment on this ticket.

Metadata