CICD: Create Auto-Build Workflows using GitHub Actions #1942
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.
Closes #1936
This is a draft PR for #1936, creating auto-build workflows for the desktop versions of bluebubbles-app. Appologies for the long commit history (at least, long for the size of the actual changes), but unfortunately the only way to test GitHub actions is in production (although I've figured out a better way to do this so the windows workflow should not have as many commits).
At this point, the PR includes an auto-build workflow for the Linux build which runs in GitHub actions whenever a new tag beginning with the letter
v
is created. The workflow builds the linux version of the app, zipping thebundle
directory intobluebubbles-linux-x86.zip
and uploading it as an asset within the release associated with the tag.I plan to begin work on the Windows workflow now, but wanted to create the PR so my work can be properly tracked.