The extension is built and in the repo (v0.1.0). To ship it, publish to the VS Code Marketplace so people can install it from inside the editor.
Steps (owner action — needs a publisher + token)
- Create/claim the
gabrielbbaldez publisher at https://marketplace.visualstudio.com/manage (the publisher in package.json).
- Create an Azure DevOps Personal Access Token with Marketplace → Manage scope.
npm i -g @vscode/vsce, then vsce login gabrielbbaldez and vsce publish (or vsce package to produce a .vsix to sanity-check first).
- Add a 128×128
icon to package.json (the Marketplace listing wants one — distinct from the monochrome activity-bar media/icon.svg).
Nice to have before publishing
- A screenshot/GIF of the tool window in the README (Marketplace renders it).
- Consider a release GitHub Action (
HaaLeo/publish-vscode-extension or vsce publish with the token as a secret) so tagging cuts a release, mirroring how the main repo publishes to Central.
Done when
stacktale is installable from the VS Code Marketplace, and (ideally) a tagged release publishes it.
The extension is built and in the repo (v0.1.0). To ship it, publish to the VS Code Marketplace so people can install it from inside the editor.
Steps (owner action — needs a publisher + token)
gabrielbbaldezpublisher at https://marketplace.visualstudio.com/manage (thepublisherin package.json).npm i -g @vscode/vsce, thenvsce login gabrielbbaldezandvsce publish(orvsce packageto produce a.vsixto sanity-check first).iconto package.json (the Marketplace listing wants one — distinct from the monochrome activity-barmedia/icon.svg).Nice to have before publishing
HaaLeo/publish-vscode-extensionorvsce publishwith the token as a secret) so tagging cuts a release, mirroring how the main repo publishes to Central.Done when
stacktaleis installable from the VS Code Marketplace, and (ideally) a tagged release publishes it.