René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Generic Git URL configs keep percent-encoded repo names","articleBody":"## Problem\nGeneric 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.\n\n## Reproduction\nConfigure a generic Git URL such as `https://github.com/test/Project%20Name%20With%20Spaces.git` and compile the connection config.\n\n## Expected\nThe direct URL path should match the existing file-based generic Git behavior and derive `github.com/test/Project Name With Spaces`.\n\n## Actual\nThe direct URL path keeps `%20` in `name`, `displayName`, and zoekt metadata.\n\n## Impact\nThe 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.","author":{"url":"https://github.com/DivyamTalwar","@type":"Person","name":"DivyamTalwar"},"datePublished":"2026-06-29T09:37:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1384/sourcebot/issues/1384"}