-
Notifications
You must be signed in to change notification settings - Fork 106
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
Discuss new CI options #522
Comments
Github Actions are what 262 is planning to move to (tc39/ecma262#2260). |
Thanks for the link. My preference is to reuse the same for consistency. |
leobalter
added a commit
that referenced
this issue
Jan 6, 2021
leobalter
added a commit
that referenced
this issue
Jan 6, 2021
Fixes #522 Co-authored-by: Jordan Harband <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Travis-CI hasn't been welcoming for our current PRs.
I'd like to migrate our CI work to GitHub Actions but I'm open to other suggestions.
We need to preserve our current PR builds and the build on the master branch that pushes the spec text to gh-pages.
The text was updated successfully, but these errors were encountered: