3 subject="""comment 1"""
4 date="2022-06-08T16:55:50Z"
6 Hmm, I think this only works for ssh:// urls currently.
8 Even the ssh url form host:/path does not work, because it gets
9 normalized to a ssh:// url.
11 The implementation does not support non-url's at all; the provided location
12 is treated as an url (`Git.Url location`). And even if it were treated as a
13 path, the path gets normalized to a relative path and an absolute path (or
14 differently relavatized path) would not work.
16 Using paths with this is rather problematic too, because if the repo is
17 cloned to another machine, it would not find the repo at the recorded path.
18 Similarly, relative paths are also problimatic. But it may as well support
19 them to the extent it can.
21 I think this needs changes to the core Git data structure, to store the
22 original, unmodified git.remote.path. Or a different interface than the
23 current, one that accepts any repo location and probes it to find the uuid.
24 The latter idea seems better because it simplifies the UI rather than
25 complicating the internal representation.