Problem
Generic Git connection configs that point directly at an HTTP(S) remote derive repo names from the raw URL pathname. If the remote path contains encoded characters, such as %20, Sourcebot stores names like github.com/test/Project%20Name instead of the decoded repo name.
Reproduction
Configure a generic Git URL such as https://github.com/test/Project%20Name%20With%20Spaces.git and compile the connection config.
Expected
The direct URL path should match the existing file-based generic Git behavior and derive github.com/test/Project Name With Spaces.
Actual
The direct URL path keeps %20 in name, displayName, and zoekt metadata.
Impact
The same remote can produce inconsistent Sourcebot/zoekt repo identifiers depending on whether it is configured as a direct URL or discovered from a local repository origin.
Problem
Generic Git connection configs that point directly at an HTTP(S) remote derive repo names from the raw URL pathname. If the remote path contains encoded characters, such as
%20, Sourcebot stores names likegithub.com/test/Project%20Nameinstead of the decoded repo name.Reproduction
Configure a generic Git URL such as
https://github.com/test/Project%20Name%20With%20Spaces.gitand compile the connection config.Expected
The direct URL path should match the existing file-based generic Git behavior and derive
github.com/test/Project Name With Spaces.Actual
The direct URL path keeps
%20inname,displayName, and zoekt metadata.Impact
The same remote can produce inconsistent Sourcebot/zoekt repo identifiers depending on whether it is configured as a direct URL or discovered from a local repository origin.