-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Meta: migrate from travis-ci to Github Actions #2260
Conversation
24e6a1a
to
d5dc0cc
Compare
to make this work properly, you eventually need to manually disable the old expected checks from TravisCI or they will remain eternally waiting for status. Disregard if you already know this, it's just trauma from an event in the past. |
Yes, as soon as this PR is ready to land, I'll make the actions checks "required" and the travis checks no longer required, but as soon as I do that, every PR will be unmergeable until they're rebased, so it's the last step before/during merge. |
Deprecate project as: * Travis CI's new pricing plan¹ has effectively dropped support for open source, so people are migrating² away from Travis CI (I did the same quite some time ago). * This project hasn't been maintain in years, nor are there any plans to do so in the future. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ¹ https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ² ljharb/object.assign#81 tc39/ecma262#2260 Close: #30 Close: #31 Close: #32 Close: #33 Close: #34
Deprecate project as: * Travis CI's new pricing plan¹ has effectively dropped support for open source, so people are migrating² away from Travis CI (I did the same quite some time ago). * This project hasn't been maintain in years, nor are there any plans to do so in the future. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ¹ https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing ² ljharb/object.assign#81 tc39/ecma262#2260 Close: #30 Close: #31 Close: #32 Close: #33 Close: #34
6076872
to
ed611b0
Compare
3074cf6
to
d644d01
Compare
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.
Hard to review this for correctness, since it interacts with a bunch of other systems, so take my approval as "this looks reasonable as far as I can tell, let's land it and see what happens".
This is pushed directly to the default branch, because workflow_run scripts are ran from the default branch
This is pushed directly to the default branch, because workflow_run scripts are ran from the default branch
This is pushed directly to the default branch, because workflow_run scripts are ran from the default branch
(ref ljharb/object.assign#81)
travis-ci's new pricing plan has effectively dropped support for open source repos, so we need to migrate off of it.
(To work properly, these workflows must be set to
pull_request_target
, notpull_request
, and must have a GOOGLE_API_KEY secret available, as well as GH_TOKEN - still working on this)