publish-vscode-extension
release-action
Our great sponsors
| publish-vscode-extension | release-action | |
|---|---|---|
| 3 | 4 | |
| 192 | 1,223 | |
| - | - | |
| 7.1 | 8.0 | |
| 20 days ago | 6 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
publish-vscode-extension
-
VS Code or VS Codium - Which should I use?
I have written a number of extensions, and I use the publish-vscode-extension GitHub action to publish my extensions to both marketplaces.
-
GitHub Action You Need to Publish VS Code Extensions
Lastly we will package and publish our extension using the Visual Studio Code Extension Manager and a GitHub Action called HaaLeo/publish-vscode-extension. The advantage of having the packaging and publishing step separated is that we can attach the compiled .vsix file as an artifact to the workflow and offer it as download. Make sure to generate a token (named in the workflow as VSC_MKTP_PAT and OPEN_VSX_TOKEN) to allow GitHub to publish your extension.
-
Write a VS Code extension in JavaScript, not TypeScript ^
I use this github action to automate publishing of an extension to both marketplaces, publication is triggered when the main branch is updated. There a couple of other github actions for
release-action
-
Anyone have an up-to-date GitHub Action config that uses cabal for binary releases
I was able to get this mostly working with a combination of /u/ExTex5's script here, as well as the release action here
-
Deploying Flutter applications to Google Play using Github actions
After all of that is done we create a release using the release-action action, located here and upload the app bundle we just generated as it will be needed in the next workflow step.
-
GitHub Action You Need to Publish VS Code Extensions
To conclude our release workflow we push our release commit and the new git tag back to GitHub, as well as attach the compiled extension file to the workflow using the ncipollo/release-action GitHub Action. This is intentionally done at the end of the workflow so that in case something went wrong during the process we don’t mark it as a new release:
- [Help Needed] How to update an existing release using Github Actions?
What are some alternatives?
tabout - Tab out of quotes, brackets, etc for Visual Studio Code
vscode-marquee - 💡 The missing VS Code homescreen that helps you to stay organized with minimal context switches
vscode-git-graph - View a Git Graph of your repository in Visual Studio Code, and easily perform Git actions from the graph.
GitVersion - From git log to SemVer in no time
vscode-vsce - VS Code Extension Manager
flatpak-vscode - Integrate Flatpak with VSCode
release - Generate a GitHub workflow that automatically makes releases for your Haskell project.
publish-extensions - Scripts for publishing VS Code extensions to open-vsx.org
flutter-action - Flutter environment for use in GitHub Actions. It works on Linux, Windows, and macOS.
vscode-extension-samples - Sample code illustrating the VS Code extension API.
fourmolu - A fourk of ormolu that uses four space indentation and allows arbitrary configuration. Don't like it? PRs welcome!