Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow non-regular GitHub host #1

Open
yermulnik opened this issue Dec 18, 2024 · 0 comments
Open

Allow non-regular GitHub host #1

yermulnik opened this issue Dec 18, 2024 · 0 comments

Comments

@yermulnik
Copy link

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:

[url "github.com-EMU:my-current-job-org/"]
    insteadOf = [email protected]:my-current-job-org/

Which has its counterpart in SSH 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant