-
-
Notifications
You must be signed in to change notification settings - Fork 109
Use Github actions instead of Travis CI (#278) #292
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 instead of Travis CI (#278) #292
Conversation
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.
Thanks for handling this!! I made a few comments but it looks very promising.
622100f
to
fa1432e
Compare
Changes done. Do you want that the release workflow create the release or just upload release asset ? |
If it can create the release when a tag is created it's even better |
fa1432e
to
cbf35de
Compare
The release workflow has been changed : it creates now a new release when a tag is pushed, and still upload release assets (schema.phar). I'm not sure what to do about the changelog, should it be generated automatically or manually by a maintainer ? |
Thanks @johnkrovitch! Regarding the changelog, we currently handle it manually. |
Hi,
the goal of this PR is to move the CI from Travis CI to Github Actions. It aims to have the same behavior than Travis (#278).
Two worklows has been created :
Note :