libgit2 / libgit2/libgit2sharp
Fetch with url throws "not a valid remote name".
Open
Nobody has claimed this yet.
Up for grabs
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Nothing much to tell, fetch with url is not working.
Example:
Repository.Network.Fetch("https://github.com/libgit2/libgit2sharp.git", new[] { "+refs/remotes/test:refs/heads/master" });
Exception:
InvalidSpecificationException: 'https://github.com/libgit2/libgit2sharp.git' is not a valid remote name.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at Repository.Network.Fetch and reproduce the issue with the URL and refspec shown in the example. Trace how the fetch source is interpreted and verify the expected behavior when the source is a URL rather than a remote name. Done means the example no longer raises InvalidSpecificationException and the fetch completes as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100