Skip to content
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

Merged
merged 4 commits into from
Feb 19, 2024

Conversation

MysteryBlokHed
Copy link
Member

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.

@MysteryBlokHed MysteryBlokHed changed the title [ci] Run lint rules on opened *and* reopened PRs [ci] Update lint rules for PR Feb 18, 2024
Copy link

netlify bot commented Feb 18, 2024

Deploy Preview for colorjs ready!

Name Link
🔨 Latest commit a0433bd
🔍 Latest deploy log https://app.netlify.com/sites/colorjs/deploys/65d298b0c1318d000804fcf8
😎 Deploy Preview https://deploy-preview-444--colorjs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@MysteryBlokHed MysteryBlokHed changed the title [ci] Update lint rules for PR [ci] Update lint rules for PR's Feb 18, 2024
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.
Copy link
Member

@jgerigmeyer jgerigmeyer left a 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. 😕

@jgerigmeyer jgerigmeyer merged commit 877ab8b into color-js:main Feb 19, 2024
5 checks passed
@MysteryBlokHed MysteryBlokHed deleted the ci/update-lint-pr-rules branch February 19, 2024 17:08
@MysteryBlokHed
Copy link
Member Author

MysteryBlokHed commented Feb 19, 2024

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 types values for the pull request trigger, but only a couple had an actual explanation as to what they were.

jgerigmeyer added a commit that referenced this pull request Feb 19, 2024
* main:
  [ci] Update lint rules for PR's (#444)
  Parse both dashed-ident and ident versions, and add missing dashed-idents to color spaces. (#439)
  [types] Fix formatting in `toGamut.d.ts` (#445)
  [types] Add JSDoc based on website docs (#436)
ardov pushed a commit to ardov/color.js that referenced this pull request Feb 27, 2024
* [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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants