libgit2 / libgit2/libgit2sharp
Repository.ListRemoteReferences needs CustomHeaders setting option
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Similar to FetchOptions used for PullOptions, CloneOptions or PushOptions, Repository.ListRemoteReferences needs to somehow expose a CustomHeaders option. Without it, a request to an on-premise Azure DevOps Server (in my case version 2020), throws the following exception using a Personal Access Token for authentication.
Unhandled exception: too many redirects or authentication replays | LibGit2Sharp.LibGit2SharpException | too many redirects or authentication replays
CustomHeaders are needed to enforce Basic Authorization.
Thank you.
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 the Repository.ListRemoteReferences entry point and compare its option flow with FetchOptions used by PullOptions, CloneOptions, and PushOptions. Trace how CustomHeaders reaches requests, then verify that callers can enforce Basic Authorization for on-premise Azure DevOps Server without authentication replays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100