Fetch with url throws "not a valid remote name".

Open
#1,488 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, git
Domain
api

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.

Description

Up for grabs

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.

Dominant language
C#
Stars
3.5k
Forks
925
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libgit2/libgit2sharp

All issues in libgit2/libgit2sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.