Consider becoming a verified publisher
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Hi VS Code PM Here 👋
Consider becoming a verified publisher. More details about this can be found here
https://code.visualstudio.com/api/working-with-extensions/publishing-extension#verify-a-publisher
We would love this to happen, so let us know if we can help somehow from the VS Code side.
Thank you
fyi @chgill-MSFT
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 linked VS Code documentation on verifying a publisher and review the extension's publishing setup. Done means the publisher is verified in the VS Code Marketplace, with any required confirmation reflected in the extension listing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100