Github authentication grammar is ambiguous - resulting in failure
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
It is not possible to reference an entire private github repository using the github source.
Repro steps
Please provide the steps required to reproduce the problem
- Have a private github repo
github you/cantTouchThis hammerTimeintopaket.dependencies- wherehammerTimeis the credential key for a valid github username/PAT combination.dotnet paket installfails with a 404 from github.
Expected behavior
This should work the same as github you/areMySunshine - where areMySunshine is a publically visible repo.
Actual behavior
Github's API fails with a 404, since it attempts to check for a file that doesn't exist.
Known workarounds
Use the git source, referencing the full github URL and with the same username/PAT credentials added.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the github you/cantTouchThis hammerTime entry in paket.dependencies with dotnet paket install, then compare it with the public-repository form and the documented git workaround. Trace the GitHub source parsing and authentication path; done means a private repository can be referenced as an entire repository without requesting a nonexistent file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100