build workflows via Github Actions #107
Merged
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.
This branch introduces some Github Actions Workflows to build packages for
The workflows trigger on push events, as well as when dispatched manually.
When new version tags are introduced, the results of the builds get packaged and offered for download as a new Release on GitHub.
CodeQL workflow now triggers on pushes and pull-requests. It can be used to check for simpler errors and if the code does compile.
Travis CI workflow got removed, as there are no more free CI services.
Appveyor workflow was removed, because of Cygwin binaries are built now via Github Actions.
As no changes to actual code were introduced, merging will be done shortly after pull.
This pull request is just for reference.