oh --repo inside a checkout ignores the checkout's hub, CA and token issue #51
closed: completed andymccall opened this · 0 comments
andymccall
The likely cause of metalgear feedback issue #19. In a checkout whose remote points at the hub, oh --repo OWNER/NAME asks 'which hub?', and with --hub it fails on the certificate, because --repo skips the checkout's remote entirely. When --repo names a repository on the same hub as a checkout remote, oh should take that remote's hub, CA and token (and, generally, a saved or remote CA for the same host).
The likely cause of metalgear feedback issue #19. In a checkout whose remote points at the hub, oh --repo OWNER/NAME asks 'which hub?', and with --hub it fails on the certificate, because --repo skips the checkout's remote entirely. When --repo names a repository on the same hub as a checkout remote, oh should take that remote's hub, CA and token (and, generally, a saved or remote CA for the same host).