search

seveas / git-spindle

Abandoned command-line interface to GitHub and other central git services
Other
172 stars 35 forks source link

fix forking of GitLab repositories #156

Closed Vampire closed 6 years ago

Vampire commented 7 years ago

According to GitLab support forking on GitLab is a two-step process. Forking via API copies the metadata, but the actual code fork is done asynchronously. This second step can need some time, depending on size of the repo and load of the systems. It is also a requirement to be able to fetch or clone. Unfortunately there is no way to watch the fork status according to GitLab support, so try for 2 minutes once a second to clone or fetch the new fork. Until then the code fork should usually be finished.

seveas commented 7 years ago

GitHub and GitLab have the same problem, also for repo creation. I like the solution, but not as an unconditional wait. Maybe have a git lab fork --wait ?

seveas commented 7 years ago

Actually, that comment is pointless. We're going to have to wait, but I'd like to fix that in a slightly different way.

seveas commented 6 years ago

Alternative solution implemented in 242d9f3, thanks!