-
Notifications
You must be signed in to change notification settings - Fork 113
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
Build: Use GitHub Actions for CI/CD #255
Conversation
ea0f75e
to
555662b
Compare
This passes the Actions CI. Travis is failing as it is trying to support older versions of Node, but it also passes the more recent builds. I'd say this is good to go, maybe with a ✅ from @chaijs/core? |
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.
Should we remove the travis config or drop the earily node versions is as well in this commit? We'll have to at least disable publishing I think.
Co-Authored-By: Austin Cawley-Edwards <[email protected]>
28dbb7d
to
5189106
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.
Looks great!
@chaijs/core sorry to ping you all, but does anyone have a chance to take a look at this? There's continued interest in adding PRs (#259) and just hoping we can get this in before blocking any of them. Thanks! |
I'll just go ahead and merge this one 😆 |
This uses GitHub Actions with the new CI/CD features to test and deploy chai-http to npm
It attempts to mimic the existing travis.yml as closely as possible.
To clarify where the tokens exist; they're in the settings page for this repo under "Security Tokens".
NPM_TOKEN
exists in there, butgithub_token
is managed automatically by GitHub Actions.