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
In our setup with Gerrit (however, I believe this may apply to other types as well) there is one main domain and many local replicas. The replicas are used for fetching, the main one is used for pushing and other Gerrit operations (including REST API, review query, etc.)
It seems however GitLens doesn't support such an approach. Instead, it keeps using the fetch remote to form the Gerrit Id: links. Moreover, due to issue #1787 even the mirror domain is broken.
The text was updated successfully, but these errors were encountered:
To complete the analysis from #1954, with the setup of the main server and mirrors GitLens configuration should mention only the main server - the one used for pushing.
In our setup with Gerrit (however, I believe this may apply to other types as well) there is one main domain and many local replicas. The replicas are used for fetching, the main one is used for pushing and other Gerrit operations (including REST API, review query, etc.)
It seems however GitLens doesn't support such an approach. Instead, it keeps using the fetch remote to form the
Gerrit Id:
links. Moreover, due to issue #1787 even the mirror domain is broken.The text was updated successfully, but these errors were encountered: