When users copy a GitHub/GitLab/etc. repository URL from a browser tab it can include UI-only query strings or fragments, for example:
https://github.com/profullstack/sh1pt?tab=readme-ov-file#usage
resolveInput() currently classifies that as kind: 'git', but preserves the query/fragment in value. That means later clone flows can pass the browser URL suffix to git clone instead of the clean repository URL.
Expected: git clone targets should normalize to the repo URL without query strings or fragments, while ordinary live-site URLs should keep their query/fragment.
When users copy a GitHub/GitLab/etc. repository URL from a browser tab it can include UI-only query strings or fragments, for example:
https://github.com/profullstack/sh1pt?tab=readme-ov-file#usageresolveInput()currently classifies that askind: 'git', but preserves the query/fragment invalue. That means later clone flows can pass the browser URL suffix togit cloneinstead of the clean repository URL.Expected: git clone targets should normalize to the repo URL without query strings or fragments, while ordinary live-site URLs should keep their query/fragment.