-
Notifications
You must be signed in to change notification settings - Fork 134
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
Move CI to Github Actions #267
Comments
It appears that the Appveyor checks may have been tied to @sschuberth's Appveyor account, which was recently deleted. So there is a high chance that those checks are now permanently broken. |
@licquia @pombredanne Thoughts on the move? |
Indeed, sorry for that 😞 @maxhbr just pinged me on the breakage.
They should be gone now. They are no more required checks, and I just deleted the dangling webhook from this repo's settings. 👍 for moving to GitHub actions (for all platforms). |
No problem @sschuberth, thanks for initially setting it up and getting it to run. Your contributions are very valued! |
Cool, thanks for removing them! We will take this as extra incentive to move to Github Actions quickly 😅 |
Maybe this could help here: https://github.com/actions/importer-issue-ops |
fixed by #410 |
Currently, Appveyor is broken, and supposedly it is not the first time that it's unstable.
Many people consider Github Actions a better CI solution than CircleCI.
For these two reasons, I'd suggest to move all CI checks to Github Actions. It seems to support runners for Linux, MacOS and Windows: https://github.com/actions/runner-images
The text was updated successfully, but these errors were encountered: