-
Notifications
You must be signed in to change notification settings - Fork 17
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(eslint): only run circular dependency check on CI #421
Conversation
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.
Don't we need to set the env variable somewhere, like in a GitHub workflow?
Sorry, I assumed that env var wasn't there because I didn't see any changes for it. But I see we have it already:
ui/.github/workflows/dhis2-verify-lib.yml
Line 14 in 4aaac38
CI: true |
So, these changes look good to me, but I'll let @varl approve (or request changes).
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
That shouldn't even be necessary, the GH actions docs have it listed as always set to true under their default env vars for runner environments. |
Thanks for pointing that out. |
N.p. 👍. That's how I interpret the docs at least. But maybe I'm missing sth. Or the defaults have changed. I'll wait for Viktor's feedback. |
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 alright to my eyes.
🎉 This PR is included in version 6.0.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.0.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
This runs our circular dependency checks only on CI, to not slow down editors, as the checks can be very cpu intensive.
See the GH docs for the
CI
env var I'm using: GH actions docs. Besides GH actions,CI
is a pretty common env var for indicating that code is running on CI so it should even work with most other providers. See also here: https://github.com/watson/ci-info/blob/master/index.js#L52.Follow up
Also, as a follow up and if this works out, we can move this and related rules to cli-style and make it a rule we check for all our codebases: https://jira.dhis2.org/browse/CLI-19