GitHub actions workflow to automate build #156
Conversation
This file contains hidden or 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
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Vibe-coded a GitHub actions workflow using Cursor to automatically build the
.zipand.dmgrelease assets. This workflow is triggered under the following conditions:masterFor 1-3, the built assets are available as artefacts on the GitHub actions run itself.
For releases, the assets are added to the release. See https://github.com/ewels/FastQC/releases/tag/v1.234 for an example:
Should all be fully automated, just to make life a little easier.
Warning
I confess I haven't actually checked the built assets much to see if they're functional. I tried with the MacOS DMG but nothing happens when I double click the icon. I get the same behaviour when I try with one of the official releases off the Babraham site though.. 🤷🏻♂️