microsoft / microsoft/vscode-remote-release
Support forks in cloneInVolume links
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
A lot of OSS repos use forks as a primary part of their developer workflows. It'd be really neat if links like https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/vscode could support a developer opening their own fork as opposed to the upstream repo.
I've started opening PRs to add Dev Container configurations to OSS repos I contribute to and I'd love to be able to add links like the "click here" in https://github.com/microsoft/vscode#development-container to repo docs. That would make the getting started developer experience for contributions super simple!
cc: @bamurtaugh
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 cloneInVolume link handling used by the vscode.dev redirect URL and trace how the repository URL is interpreted. The change is done when a developer can use the link with their own GitHub fork, while the existing upstream-repository flow continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100