Publish to Open VSX Registry
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript, vscode
Research direction
Start with the linked Open VSX publishing instructions and inspect the repository's extension package metadata to identify the publishable artifact. Done means the "Copy Text of Selected Files" extension is published to the Open VSX Registry and available for compatible VS Code forks.
Written by the indexing model from the issue text.
Description
Please consider publishing thhe "Copy Text of Selected Files" extension to the Open VSX Registry?
Then it can be used with VSCode forks, like Cursor, Google's Antigravity, VSCodium, Windsurf, etc. Those IDEs have many millions of users.
Instructions are here.
Thank you!
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100