upload-release-asset
memrise-audio-uploader
| upload-release-asset | memrise-audio-uploader | |
|---|---|---|
| 5 | 3 | |
| 573 | 14 | |
| - | - | |
| 0.9 | 0.0 | |
| about 3 years ago | over 1 year ago | |
| JavaScript | JavaScript | |
| 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.
upload-release-asset
-
GitHub Action to compile binary and create release
is it possible to write a GitHub Action that would compile my Rust binary for 3 different systems (Mac, Linux and Windows), create a new release on GitHub and upload those binaries to it? I've found this action, and also this one. Those seem to be able to do what I need, but they are both archived and not actively maintained for quite a while. Is it even safe to use those? I know that Actions can be used to compile my binaries as I've already been using them to run tests on all three systems, but I want to know if it is possible upload those binaries and create release with them. Also, is it possible to read version number from a file in my repository with GitHub Actions to set that as a name for a new release?
-
The main workflow
Call upload-release-asset to upload zip asset to the release (to be used by publish-on-chrome-web-store and publish-on-firefox-add-ons workflows later).
-
upload-release-asset VS RadarKit - a user suggested alternative
2 projects | 21 Jan 2022
-
Creating GitHub release
All 3 steps use the same upload-release-asset action to add an asset to the release by its upload_url extracted from createRelease step's output. To provide asset_path we use outputs of corresponding steps which contain absolute path to artifacts.
-
Adding .Net artefacts to a release automatically with GitHub Actions
I followed the instructions on the upload-release-asset action, but never got it to work. Has anyone else got it working, so I can have a look at their .github-actions.yml?
memrise-audio-uploader
-
The main workflow
Any comments, critics and sharing your own experience would be appreciated. You can find a real example of the described CI/CD approach in my Memrise Audio Uploader extension.
-
Releasing WebExtension using GitHub Actions
I'm the author of an open-source browser extension and I want to share the workflow that I have created for:
-
Bonus. Retry of Chrome Web Store releasing steps
You can find the final version of the workflows in (memrise-audio-uploader)[https://github.com/cardinalby/memrise-audio-uploader] repo that was a prototype and a guinea pig for this article.
What are some alternatives?
create-release - An Action to create releases via the GitHub Release API
memrise-audio-uploaderdesign
setup-ruby - An action to download a prebuilt Ruby and add it to the PATH in 5 seconds
HomeAutio.Mqtt.GoogleHome
WorkFlowGenerator - A .NET global tool to generate workflows for GitHub Actions based on project configuration and user inputs
create-banner-image - An easy way to make banners from articles that you make with only 1 step!
Django_AWS_Lightsail_Template - Simple Template to deploy Django Apps to AWS Lightsail through Github Actions
Ecobee
keepalive-workflow - GitHub action to prevent GitHub from suspending your cronjob based triggers due to repository inactivity
RadarKit - The Radar Kit allowing you to locate places, trip neary by you Or it will help you to search out the people around you with the few lines of code..!!!
dependaware - DependAware: Automated NPM dependency updates with pull requests, testing, and PR descriptions for a secure and up-to-date project.
manual-approval - Pause your GitHub Actions workflow and request manual approval from set approvers before continuing