The change in https://github.com/openjdk/skara/pull/1226 tried to make "git sync" be more careful about which remotes it automatically would sync between. Unfortunately, it's a bit too restrictive. The API call to get the fork parent from one of our forges requires authentication, which we do not have available in this context. Skara also fails to extract any proxy configuration from the underlying git config, which further impairs usability inside Oracle for Github repos. Skara also has to do some trial and error to identify the correct forge provider, which makes the probing take considerable time. I don't think it's ok for the command to spend 10s+ doing seemingly "nothing".
I'm not sure what the best solution is here yet.
I'm not sure what the best solution is here yet.
- duplicates
-
SKARA-1232 git sync unable to determine fork relationship over ssh
- Closed
- relates to
-
SKARA-1232 git sync unable to determine fork relationship over ssh
- Closed