-
Notifications
You must be signed in to change notification settings - Fork 9
Handle GitLab remotes on non-gitlab hosts/domains #76
Comments
The domain specified in the config file has been added for processing See #76
Thanks for the contribution. Your opinion is very informative. I added the ability to virtually define gitlab domain as a solution. You can try this on the following branch. The virtual gitlab domain feature adds the domain set in the lab command's configuration file to gitlab remote automatic detection.
For example, |
Thanks @lighttiger2505, much appreciated! How would this work in the What do you think? Just trying to make this feature as easy as possible for people to use. |
Thanks for an interesting tool!
For me, the usefulness is a bit limited since our (internal) GitLab server is not named
gitlab.foo.bar
but insteadgit.foo.bar
, so the heuristics for auto-detecting the GitLab remote does not workI did the following local tweak which works for me but is rather silly (I have an
origin
remote which is my personal fork and anupstream
remote which is the main repository). If we could find a way to conditionalize this (perhaps with a config parameter or ENV variable), it would be great and increase the usefulness of the tool. Do you have any ideas?The text was updated successfully, but these errors were encountered: