-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Host association compatibility with ".ssh/config" #293
Comments
Reading the correct host from config might be some effort, but if we could at least just override the hostname per project that would be already great. Edit: actually there is a workaround. I created another origin, called it "real" and told gitlink to use this origin, now it works. |
I have the same problem(kinda)
the plugin uses will be great if we could globally configure the plugin to delete prefix/suffix from the |
Having a hostname override option in the plugin settings would be the easiest solution for this as @Vistritium suggested. This could be a simple input box in the project level settings or a map option at the application level that lets you specify multiple hosts, for example, |
When using different ssh keys associated to different profiles, it's usually the norm that people configure their
.ssh/config
file like so:Making it such that if the repo is cloned using:
git clone dev:org/project.git
The dev hostname is not correctly resolved and has to be set manually.
This is not a big inconvenience but it would be nice if GitLink is able to parse the config file and understand the real platform that a particular ssh profile/key is being used for.
The text was updated successfully, but these errors were encountered: