Remote Url transport behaviour/documentation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 450
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
I am trying to pull from local repos using relative remote urls like ../my_other_repo. remote.download() fails with Unsupported URL protocol. The standard git cli doesn't do this, and seems to store relative paths as such in the config file. Converting to file:///absolute/path/to/my_other_repo seems to work. Can anyone confirm that I'm on the right track and, also, is there any way to know which transports are supported/required?
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 with the remote.download() entry point and reproduce the relative URL failure described in the issue. Compare that behavior with file:/// URLs, then document which transports are supported and how relative remote paths are handled; done means the behavior and supported transports are clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, rust
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100