[rush] Running any kind of `rush change` command yields "Unable to find a git remote matching the repository URL"

[kgetz-arista]

Summary

If I run any rush change command, I get this warning:

Unable to find a git remote matching the repository URL (redacted). Detected changes are likely to be incorrect.

The URL printed in the warning is the correct URL. I'm not sure why Rush can't find it.

Details

The commands might still be working correctly, but this warning is very annoying. Is there a way to figure out why it's being printed?

Standard questions

Please answer these questions to help us investigate your issue more quickly:

Question	Answer
@microsoft/rush globally installed version?	5.169.3
rushVersion from rush.json?	5.169.3
pnpmVersion, npmVersion, or yarnVersion from rush.json?	10.32.1
(if pnpm) useWorkspaces from pnpm-config.json?	true
Operating system?	Windows 11
Would you consider contributing a PR?	No
Node.js version (node -v)?	24.12.0

[kgetz-arista]

For a bit more context: we use SSH-based cloning on our laptops, but our CI system uses HTTP-based cloning. AFAIK we can specify only one URL in rush.json so I'm not sure how this command will run warning-free in all scenarios.

[tluma]

The documentation states that rush change uses the repository.url from rush.json to find the correct git remote for comparison. If the URL in rush.json doesn't exactly match what your git remote is configured to (as shown by git remote -v), you'll get this warning.

Common causes of a mismatch include:

• Trailing .git suffix differences (e.g., https://github.com/org/repo vs https://github.com/org/repo.git)
• SSH vs HTTPS format differences (e.g., git@github.com:org/repo vs https://github.com/org/repo)
• Case sensitivity in the URL path

You can verify by running git remote -v and comparing the URL to what's in your rush.json repository.url field.

Also what will be if you will try to git clone your URL manually with git? (you need to test one to one - if it will work manually it will work in rush too).

PS: after your update, why not using ssh everywhere?