Move CI to Github Actions #601
Closed
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 CI is still configured to use TravisCI, although it hasn't built in the past 9 months. Since Travis stopped offering generous free plan for open source, most projects have moved to GitHub actions, which seems to be the default these days.
This migrates the existing Travis config to GitHub actions.
The build status isn't reported due to security reasons from GitHub: a workflow added from a fork isn't running. You can see the build result on my fork: https://github.com/browniebroke/python-future/actions/workflows/ci.yml?query=branch%3Aci%2Fgh-actionsActually it seems to be triggering now 👀