Skip to content

Simplify matching GitLab projects with git remotes

Problem to solve

When the GitLab instance isn't on the same host as the git remote, the extension can't match git remote with the GitLab instance URL because this matching is based on the host.

For example, if git remote is on git@git.something and the instance on https://gitlab.something, the user has to manually assign each remote to it's GitLab project. The user has to do this for every project on that GitLab instance.

Proposal

If the user manually assigns git@git.something with a project on https://gitlab.something, we could add an extra step that would ask "Would you like to always assign git.something remote URLs with gitlab.something GitLab instance? And if the answer is yes, we could add a setting to the global settings.json. Maybe something like: "gitlab.manuallyMatchedHosts": {"gitlab.something": "git.something"}

Further details

Links / references

Edited by Tomas Vik (OOO back on 2025-01-02)