Proxy support for HTTP transport for `.clone_at` in rugged?
Open
Nobody has claimed this yet.
libgit2
- Dominant language
- C
- Stars
- 2.3k
- Forks
- 293
- PR merge metrics
- No merged PRs in 30d
Description
Is there any chance to support HTTP-transport via proxy in rugged for Rugged::Repository.clone_at('http://example.org/repo.git')? There's an issue open at libgit2/libgit2#2555, but maybe that would be something which can / needs to be "fixed" in rugged itself.
Cheers,
dg
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 with Rugged::Repository.clone_at('http://example.org/repo.git') and review libgit2/libgit2#2555 to determine whether proxy support belongs in rugged or libgit2. Done means HTTP cloning through a configured proxy works through this API, with coverage added wherever the repository's clone tests live.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, git, ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100