You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my repository I use GitHub Actions to compile a few firmwares with a set of flags to build binaries for three common Arduino Nano clones.
This action is triggered when a new tag is pushed with the semantic version pattern, like "vX.Y.Z". After the binaries are created, a new GitHub release is added and all of the firmware binaries are attached to the release.
I would like to be able to use the GitHub latest release assets as the source of my .hex files with the arduino-web-uploader library.
Here is the GitHub action file I use to build the binaries, create the release, and attach the binaries to the release assets.
In my repository I use GitHub Actions to compile a few firmwares with a set of flags to build binaries for three common Arduino Nano clones.
This action is triggered when a new tag is pushed with the semantic version pattern, like "vX.Y.Z". After the binaries are created, a new GitHub release is added and all of the firmware binaries are attached to the release.
I would like to be able to use the GitHub latest release assets as the source of my .hex files with the arduino-web-uploader library.
Here is the GitHub action file I use to build the binaries, create the release, and attach the binaries to the release assets.
https://github.com/awonak/HagiwoModulove/blob/main/.github/workflows/build_release.yml
Related issue: modulove/A-RYTH-MATIK#10
The text was updated successfully, but these errors were encountered: