You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using GitHub EMU here at my current job and to not mess it with my personal GitHub account I use custom GitHub hostname by means of below GIT CLI config:
Host github.com-EMU
HostName github.com
User git
[…]
prowl trips over this:
> gh prowl --help
failed to initialize cli:unable to determine current repository, none of the git remotes configured for this repository point to a known GitHub host
I guess GH CLI extensions should have an option to rely internally upon the authentication data provided by the gh auth set of commands or somehow otherwise be able to fall back to default GH host (github.com) maybe. Also what I've seen from other extensions, that are based on GH Go lib(s), is that they either provide a command line flag to supply GH hostname, or provide flag like below:
-R, --repo string target repository in '[HOST/]OWNER/REPO' format (defaults to the current working directory's repository)
Would appreciate if you could look into this when you have a moment. Thanks.
The text was updated successfully, but these errors were encountered:
We're using GitHub EMU here at my current job and to not mess it with my personal GitHub account I use custom GitHub hostname by means of below GIT CLI config:
Which has its counterpart in SSH config:
prowl
trips over this:I guess GH CLI extensions should have an option to rely internally upon the authentication data provided by the
gh auth
set of commands or somehow otherwise be able to fall back to default GH host (github.com
) maybe. Also what I've seen from other extensions, that are based on GH Go lib(s), is that they either provide a command line flag to supply GH hostname, or provide flag like below:Would appreciate if you could look into this when you have a moment. Thanks.
The text was updated successfully, but these errors were encountered: