{"version":"2.1.223","anchor":"git-remote-url-parsing-normalizes-leading-slashes-and-percen","canonical_anchor":"git-remote-url-parsing-normalizes-leading-slashes-and-percen","heading":"Git remote URL parsing normalizes leading slashes and percent-encoding","tier":"notice","area":"Git Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/git-remote-url-parsing-normalizes-leading-slashes-and-percen","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Git remote URL parsing normalizes leading slashes and percent-encoding\n\nGit remote URLs differing only by a slash or escaping now resolve to the same repository.\n\n**What**\n\nRemote URLs that differ only by a leading slash or percent-encoding now resolve to the same repository identity, and malformed paths are rejected rather than half-parsed.\n\n**Details**\n\n- The scp-style parser strips leading slashes from the path.\n- The owner\/repo result must split into exactly two non-empty segments, otherwise parsing returns null.\n- The URL-form sanitizer attempts `decodeURIComponent(r.pathname)` inside a try\/catch, so a failure to decode leaves the path untouched.\n\n**Evidence**\n\n`r.pathname = decodeURIComponent(r.pathname);`\n\n- Area: Git Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}