-
Notifications
You must be signed in to change notification settings - Fork 173
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
Force CI to run on every PR #286
Conversation
Could you clarify what you mean by broken tests? I just did |
This is why we have code review :) It turns out that So, the only thing that this PR would do then is to make sure all tests run on every PR. |
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.
Generally lgtm. Some concerns about the nature of the changes but non-blockers.
Maybe this is an opportunity to move away from |
@shunkica , would you be willing to put up a PR for a migration of the tests? |
@LoneRifle , I think I've addressed all your concerns. Feel free to have another look at this. Your feedback is quite good. I look forward implementing some of this over in |
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.
lgtm, as discussed. Thanks for looking into this!
To improve code quality going forward, this PR will enable all tests to run on every PR.
In order to get tests to most closely represent an actual deployment
npm ci
is used, this, however, isn't available on older versions of Node, so the test matrix doesn't reflect the actually supported versions of Node. We should do asemver-major
change to get this version up to Node@8, at least, to be able to test all supported versions.