release-action
vscode-marquee
release-action | vscode-marquee | |
---|---|---|
4 | 4 | |
1,228 | 97 | |
- | - | |
8.0 | 5.9 | |
17 days ago | 4 months 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.
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-marquee
-
Projects Coming to Life ๐ Inside of VS Code - Marquee's Project Mode
This and the desire for better DX is what motivated us (at Stateful) to introduce relevant onboarding information readily into Marquee - the high-density information homescreen for VS Code. As of Marquee v3.2.0 the beta UX of ๐ Project Mode is available to you.
-
GitHub Action You Need to Publish VS Code Extensions
The term continuous integration and continuous delivery (short CI/CD) is a common best practice for software developers, including the ones building VS Code extensions. With the VS Code update from last November users have now access to pre-releases that allow developers to ship regular updates and offer testing out the latest cutting edge features from their extension to receive early feedback. In this blog post weโd like to share how Stateful releases its Marquee extension to the VS Code Marketplace and OpenVSX Registry through GitHub Actions. You can find a full example in the Marquee repository, feel free to copy and adapt it for your own extension.
-
The Popular VS Code Homescreen is Now Open Source
Come find us either on GitHub, our community channels on Discord & Gitter, or through the in-Marquee feedback channels. Also take a look at the roadmap to see what's on Marquee's horizon.
sounds great! let us know if you have any feature requests: https://github.com/stateful/vscode-marquee/issues
What are some alternatives?
publish-vscode-extension - GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.
vsc-memer - vscode extension for making memes inside your code
GitVersion - From git log to SemVer in no time
vscode-vsce - VS Code Extension Manager
vscode-react-javascript-snippets - Extension for React/Javascript snippets with search supporting ES7+ and babel features
release - Generate a GitHub workflow that automatically makes releases for your Haskell project.
flutter-action - Flutter environment for use in GitHub Actions. It works on Linux, Windows, and macOS.
vscode-extension-gdunit3 - Visual Studio Code Extension for GdUnit3
fourmolu - A fourk of ormolu that uses four space indentation and allows arbitrary configuration. Don't like it? PRs welcome!
Code-Server - VS Code in the browser