Build automatically using GitHub workflow #72
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.
Yet another feature that made me think that if it's useful for me, there's a chance it might be useful for others :)
This uses GitHub Actions to automatically build w64devkit.
This is the way I made it for myself, I'm open to bring modifications to the PR if something in there would be interesting.
The builds are triggered on either of two events:
Each commit pushed to master, and each pull request open to master, which upload builds to the Action page (example):
This offers a nice an easy way to download builds for any commit on the master branch. Unfortunately, those are only available for logged in users.
Each tag pushed on the repo, which automatically uploads the builds to a new release marked as draft (example - the only thing I did manually was to publish the release):
This offers a ready-made template for releases based on git tags. I tried to strictly follow the format used by the latest releases, as to minimize manual intervention, but the release is not automatically published by GitHub Actions, so manual intervention is always possible before publishing a release.
The upsides I've noticed:
The downsides:
If there's interest in this PR, I can explain in further detail any decision I took while creating the workflow file. I'm also willing to adapt this PR as necessary.