-
Notifications
You must be signed in to change notification settings - Fork 87
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 from Travis CI to GitHub Actions? #555
Comments
I didn't know about Travis CI being no longer useful. 😱 I would welcome a PR for using Github actions. I don't think it is required to add it to master first, my experience is that the changes done in a branch will trigger the actions if they are enabled in the repo. I will double check this though. |
You don't need to add it to
Which they aren't, in Edit: anyway, I'm pull request'ing. 😄 |
I misunderstood, I have now looked it up and noticed you mentioned travis-ci.org that is shutting down, but it will still be possible to use travis-ci.com for open source projects though.
AFAIU they will get triggered in the branch where the workflow is created.
|
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing: "which allows around 1000 minutes in a Linux environment." https://docs.github.com/en/free-pro-team@latest/github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions: "GitHub Actions usage is free for public repositories and self-hosted runners." (at least, until... 😄) |
You can probably check consumption here: https://github.com/organizations/inaka/settings/billing. |
This was closed the moment #558 was too. |
Would you be interested in a pull request that moves CI from Travis CI to GitHub Actions, or at least adds GitHub Actions alongside Travis CI? It seems travis-ci.org will stop being useful from Dec 31 2020. I can do it, except that I think you need to create the workflow yml, first, in
master
, after which I can branch off of.We should probably do the same for
elvis_core
if this proposal is accepted.The text was updated successfully, but these errors were encountered: