-
Notifications
You must be signed in to change notification settings - Fork 82
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
[ci] Update lint rules for PR's #444
[ci] Update lint rules for PR's #444
Conversation
✅ Deploy Preview for colorjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
For some reason, I cannot get the eslint checks to fail locally and produce the same errors as the CI did. I'm going to temporarily commit this to get the CI to run against it and see whether it passes.
This reverts commit 02cc49e. CI passed; I'll move this change to a separate 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.
Interesting -- I thought push:
would cover this case as well. 😕
I don't blame you—Honestly, I feel like some of the conditions to run CI are pretty poorly documented on GitHub's pages. I found a list of valid |
* [ci] Run lint rules on opened *and* reopened PRs * [types] Temporary commit to test CI For some reason, I cannot get the eslint checks to fail locally and produce the same errors as the CI did. I'm going to temporarily commit this to get the CI to run against it and see whether it passes. * Revert "[types] Temporary commit to test CI" This reverts commit 02cc49e. CI passed; I'll move this change to a separate PR.
A PR I just merged (#436) passed all the CI on the pull request page, but failed once it was merged into main. This is because the lint CI didn't actually run on the PR.
This change makes the CI rerun when a PR is opened, reopened, and when commits are pushed.