-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Should gh.nvim config.prefer_https_remote use gh config? #28
Comments
Aha!
That would be pretty cool, and probably the right thing to do, so you're thinking, on gh.nvim startup, do something like:
and then automatically set the git remote accordingly? |
Yes I think thats the approach |
Would you want to take on that PR? Seems relatively straight forward. |
Yeah I can do that |
Cool, we may want an "auto" flag in the "prefer_https_remotes" config value, where we dynamically look it up. This then still allows the user to force "ssh" or "https" if they want to. Maybe its useful? |
My intuition is that a user wouldn't need to define a different protocol for gh.nvim that is different than |
@David-Kunz in issue #15 you had to flip the "prefer_https_remote" flag in your private repo. In this issue we are trying to determine if we looked at the "gh config list" command and set the remote type with the setting in there, would it have set the correct remote protocol for you? Could you run that command in your private repo where you're using the "prefer_https_remote" flag and tell us the value of the "git_protocol" config. |
Hi @ldelossa, When I execute Best regards, |
Cool, thanks @David-Kunz. a little unscientific @dlvhdr but seems like on all our systems the gh cli matches the git protocol that works. Just wanted to make sure. |
Closed! Thanks again @dlvhdr |
Thank occurred just now:
Weird lol. I manually set it to get it to work again.
|
The gh config already stores the user preference for https/ssh.
Do you think you should respect that as well? as all the other actions use gh under the hood I'm assuming.
The text was updated successfully, but these errors were encountered: