-
Notifications
You must be signed in to change notification settings - Fork 295
Consolidate linting tools into single CI job #3445
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
Consolidate linting tools into single CI job #3445
Conversation
Previously, linting/formatting errors would cause multiple CI jobs to
fail simultaneously (often 7+ jobs), making it confusing to identify
the actual issue and slowing down CI feedback.
Changes:
- Created new autoformat.yml workflow that runs all linting/formatting
checks in a single job:
- TypeScript prettier formatting check
- TypeScript eslint checks (all packages)
- Elixir mix format check
- Elixir compilation warnings check
- Removed redundant linting checks from other workflows:
- ts_test.yml: Removed stylecheck and format:check from package
and example checking jobs (kept typecheck for actual type errors)
- elixir_tests.yml: Removed the separate formatting job
- integration_tests.yml: Removed --warnings-as-errors flag from
compile step
Now linting/formatting errors will only cause the single autoformat
job to fail, while other test jobs focus on functional testing.
commit: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3445 +/- ##
==========================================
+ Coverage 67.45% 73.37% +5.91%
==========================================
Files 180 28 -152
Lines 9671 1198 -8473
Branches 359 107 -252
==========================================
- Hits 6524 879 -5645
+ Misses 3145 318 -2827
+ Partials 2 1 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Separate the formatting checks into two independent jobs that run in parallel: - typescript_formatting: Prettier and ESLint checks for TS/JS code - elixir_formatting: mix format and compilation warnings for Elixir This ensures failures in one language ecosystem don't block feedback from the other, and both can run concurrently.
alco
left a comment
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.
Nice!
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…nting-ci-016xvNjnWVXhLGTq3t7u1VVD
Previously, linting/formatting errors would cause multiple CI jobs to fail simultaneously (often 7+ jobs), making it confusing to identify the actual issue and slowing down CI feedback.
Changes:
Created new autoformat.yml workflow that runs all linting/formatting checks in a single job:
Removed redundant linting checks from other workflows:
Now linting/formatting errors will only cause the single autoformat job to fail, while other test jobs focus on functional testing.