Implement Github Action for firmware build and Release Notes updates #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement GitHub actions to automatically build the BLE firmware and add it to the release assets on tagging.
Use GitHub actions to automatically generate release notes based on PRs history (release drafter)
This should simplify installation for the end users, as you can use Artemis Firmware Upload GUI to upload the firmware.
A new firmware is built on any new push to the repo, and upon release + tagging the firmware is uploaded to the release notes. For example https://github.com/Adminiuga/roast-meter/releases
Upon building, the commit hash and tag is used as a version string, to help positively identify the installed version on the device.
Let me know if you would like to split this PR into two different: one for firmware build and another for the release drafter.
I made an assumption, the BLE firmware is the recommended firmware, as it allows calibration without the need for firmware rebuild. If needed, I can add a serial & eeprom interface to the original
roast_meter.inofirmware, let me know.