Migrate CI for Travis to GitHub Actions #76
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.
The existing CI setup based on Travis does not work anymore due to Travis ending support for free CI for open-source projects.
This migrates the CI to GitHub Actions, with one job running CI for contributions, and a scheduled job checking for updates in uap-core once a day to publish an updated regexes.php file (we could change the schedule), as the Travis setup was including such an automated update.
An alternative might be to update to the latest uap-core release instead, which would be more consistent with the way uap-python works for instance.