-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate CI to github actions #49
Comments
Oh yeah, let's get off Travis ASAP. It should be straightforward since we don't need any exotic libraries here IIRC. I'll work on a PR tomorrow. |
Although I seem to recall that GHA doesn't allow network access, which would be a spanner in the works of our (arguably not particularly useful can-we-interact-with-the-API tests). |
maybe related? hyperium/hyper#1009 #48 updated hyper - maybe there is a corresponding change to make? @elwerene - Were you able to have the tests passing locally? |
Ha I just updated reqwest and hyper |
OK well I've completely confused myself now. That'll teach me to think "this will be a five minute PR". Tomorrow it is! |
no - but not on master either :/ |
Drive-by remark: wouldn't it make sense to enable |
Build is stalled: #48 (comment)
It seems like maybe bors is set up OK and has appropriate access, but the build status never updates.
I think this is because this repo still relies on travis-ci.
There's too much verbage here for me to be willing to read right now: https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
But I believe the take away is that travis-ci is no longer an option for us unless we want to pay, so I'd recommend switching to github actions instead of travis, like we have for most of our other repositories.
The text was updated successfully, but these errors were encountered: