Summary: CI is down. I suggest we switch to GitHub Actions (I'll try to finally review #82). In the meantime, can someone please disable the CI requirement (or give me admin access so I can do it myself)?
Travis CI has shut down travis-ci.org and requires projects to migrate to travis-ci.com (which was originally the paid version for private repositories). I believe the free tier for open source projects (public repositories) has been replaced with a free trial that includes one-off credits for 1000 build minutes, and additional credits need to be manually requested from the Travis CI support team, subject to requirements. (This is despite the migration guide saying that "Travis CI will continue to offer a free tier for public or open-source repositories on travis-ci.com and will not be affected by the migration.")
We would probably meet those requirements, but it sounds like it would be an ongoing hassle. I think we'd be better off switching to another service, for example GitHub Actions. There is already a great open PR (#82) for that; I started reviewing it but never finished, I'll try to finally get that done.
In the meantime, the CI outage together with our current branch protection settings prevent merges into branch 'master'. How about we disable the CI requirement for now?
Summary: CI is down. I suggest we switch to GitHub Actions (I'll try to finally review #82). In the meantime, can someone please disable the CI requirement (or give me admin access so I can do it myself)?
Travis CI has shut down travis-ci.org and requires projects to migrate to travis-ci.com (which was originally the paid version for private repositories). I believe the free tier for open source projects (public repositories) has been replaced with a free trial that includes one-off credits for 1000 build minutes, and additional credits need to be manually requested from the Travis CI support team, subject to requirements. (This is despite the migration guide saying that "Travis CI will continue to offer a free tier for public or open-source repositories on travis-ci.com and will not be affected by the migration.")
We would probably meet those requirements, but it sounds like it would be an ongoing hassle. I think we'd be better off switching to another service, for example GitHub Actions. There is already a great open PR (#82) for that; I started reviewing it but never finished, I'll try to finally get that done.
In the meantime, the CI outage together with our current branch protection settings prevent merges into branch 'master'. How about we disable the CI requirement for now?