release-action
vscode-vsce
release-action | vscode-vsce | |
---|---|---|
4 | 3 | |
1,228 | 755 | |
- | 2.4% | |
8.0 | 8.5 | |
16 days ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
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?
vscode-vsce
-
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.
-
I automated publishing my VSCode Extension
I'm using VSCE - VSCode Extension Manager package to build and deploy my project to the Marketplace.
-
Write a VS Code extension in JavaScript, not TypeScript ^
There is a CLI tool called vsce for packaging and publishing extensions. It's easy to use. This will create a vsix package that can be installed as an extension.
What are some alternatives?
publish-vscode-extension - GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.
openvsx - An open-source registry for VS Code extensions
vscode-marquee - 💡 The missing VS Code homescreen that helps you to stay organized with minimal context switches
vscode-extension-samples - Sample code illustrating the VS Code extension API.
GitVersion - From git log to SemVer in no time
release - Generate a GitHub workflow that automatically makes releases for your Haskell project.
vscode-snippets-ranger - View and edit all of your snippets in one purty place! Yee-haw!!
flutter-action - Flutter environment for use in GitHub Actions. It works on Linux, Windows, and macOS.
vscode-marky-stats - Configurable statistics of your markdown document on your status bar.
fourmolu - A fourk of ormolu that uses four space indentation and allows arbitrary configuration. Don't like it? PRs welcome!