Closed Mailaender closed 3 years ago
Considering that our outstanding plan is to move everything to github actions, is there any benefit to going (backwards?) to Appveyor?
If GitHub Actions supports Windows, then we don't need this. This is however easy to setup and very fast compared to Travis CI.
Its easy if you know how the github-appveyor integration works. I think that considering the plan to move to Github Actions asking modders to enable a service now only to remove it again on the (hopefully) next update is unnecessary disruption/churn, and updating our SDK docs to cover AppVeyor like we do for Travis isn't a good use of our time. This is best left to downstream mods who don't have to pay that maintenance cost.
using @APpveyor