René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Parsing of refspec in remote fetch configuration different from git","articleBody":"Based on an issue reported in https://github.com/dotnet/sourcelink/issues/256.\r\n\r\n### Reproduction steps\r\n\r\nAdd a configuration entry like so:\r\n\r\n```\r\n[remote \"origin\"]\r\n        url = https://github.com/somerepo.git\r\n        fetch = +refs/heads/package-*:refs/remotes/origin/package-*\r\n```\r\n\r\nand read remotes information using libgit2 APIs.\r\n\r\nThe issue is that the fetch refspec does not end with `/*`. libgit2 is able to read the configuration if the refspec does end with `/*`.\r\n\r\n```\r\nfetch = +refs/heads/package/*:refs/remotes/origin/package/*\r\n``` \r\n\r\n### Expected behavior\r\n\r\nSucceeds.\r\n\r\n### Actual behavior\r\n\r\n```\r\n'+refs/heads/package-*:refs/remotes/origin/package-*' is not a valid refspec.\r\n```\r\n\r\n### Version of libgit2 (release number or SHA1)\r\n\r\nlibgit2-a904fc6\r\n\r\n### Operating system(s) tested\r\n\r\nWindows.","author":{"url":"https://github.com/tmat","@type":"Person","name":"tmat"},"datePublished":"2019-04-22T18:28:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/5058/libgit2/issues/5058"}