Skip a remote with no URL when listing remotes [patch]

[matt-edmondson]

Fixes #175

What was wrong

git remote -v lists a remote.<name>.* config section that has no url as name<TAB>, with nothing after the tab. You get one from a global remote.origin.prune=true in a repository without an origin. GitRemoteParser threw GitParseException on that line, so Remotes() failed for the whole repository and dropped the valid remotes along with it.

Change

• GitRemoteParser.Parse now skips a line whose text after the tab is empty, which matches git treating such a remote as non-existent. Every other malformed line still throws.
• Parser test: "origin\t\nupstream\thttps://x (fetch)\nupstream\thttps://x (push)\n" returns only upstream.
• Integration test: a temp repository with remote.ghost.prune=true and no URL gets an empty list from Remotes(), with no exception.

Verification

• Both new tests fail with the parser change reverted and pass with it.
• Full suite: dotnet test passed 802 of 802.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KLFPeLz9EhDwj3AmatpfG6

---

Generated by Claude Code

[matt-edmondson]

ci / .NET / Test on macos-latest (run 38341576299) sat in its Test step for about 53 minutes with no result. I cancelled it and queued one re-run.

I don't think the hang comes from this PR. The other workflow's Test on macos-latest ran the same test suite on the same commit (1739ad5), including the new Remotes() tests, and passed in about 3 minutes. The CI macOS jobs on #209 and #210 also passed. If the re-run hangs too, I'll treat it as a real failure and investigate it.

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud