-
Notifications
You must be signed in to change notification settings - Fork 481
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
Use Github Actions as CI #461
Milestone
Comments
ataffanel
added a commit
that referenced
this issue
Dec 16, 2020
ataffanel
added a commit
that referenced
this issue
Dec 16, 2020
ataffanel
added a commit
that referenced
this issue
Dec 16, 2020
ataffanel
added a commit
that referenced
this issue
Dec 16, 2020
ataffanel
added a commit
that referenced
this issue
Dec 21, 2020
ataffanel
added a commit
that referenced
this issue
Dec 21, 2020
ataffanel
added a commit
that referenced
this issue
Dec 21, 2020
Copy the app-veyor used versions for the GH action build. Lets modernize the build as a separate step
ataffanel
added a commit
that referenced
this issue
Jan 5, 2021
ataffanel
added a commit
that referenced
this issue
Jan 5, 2021
This allows to add dependencies: the windows and Mac build will not run unless the checks passes
ataffanel
added a commit
that referenced
this issue
Jan 12, 2021
ataffanel
added a commit
that referenced
this issue
Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Github actions can work as CI for Windows, Mac and Linux. We should use GitHub actions for building windows installer as well as running tests on Linux instead of Appveyor and Travis. This will limit the amount of CI services and configuration we have to handle
The text was updated successfully, but these errors were encountered: