-
Notifications
You must be signed in to change notification settings - Fork 411
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
Unify to single CI platform #778
Conversation
This reverts commit e572b55.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi!
This looks interesting. Did you unify on appveyor only because it was easier? Or for another reason?
I ask, because Github Actions seems to be the new kid on the block everyone is talking about 😉
Yes, as I have already some experience with it.
Time. 😄
I know and I have tried it with just one project so I am barely proficient in it. Everything system needs time getting used to with some trial and error. I have been using AppVeyor for ages and it has served me well. It now supports Linux and macOS images so it was the path of least friction. I am happy to move to GitHub Actions if someone well-versed in it can help with the setup and maintenance. However, given that issue #602 has been open since over a year and no one really picked it up, I just wanted to get this sorted out for now so we can move to more interesting (less infrastructural) work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR addresses #602 by unifying on AppVeyor as the single CI platform.