Skip to content

Conversation

@pawelangelow
Copy link
Contributor

@pawelangelow pawelangelow commented Dec 18, 2025

What

Adds ESLint as a blocking step in CI before tests run:

  1. New lint.yml workflow - Runs ESLint as a required check that blocks test execution if linting fails
  2. Fix import/extensions rule - Fixed ESLint config to ignore api/dist folder
  3. Remove redundant Code analysis steps - Removed the non-blocking lint steps from frontend and backend test workflows (these only sent Slack reports, didn't block on errors)

Changes

  • Tests now wait for lint to pass before running
  • Lint failures block the pipeline (previously lint errors were just reported to Slack)
  • Faster feedback - lint runs in parallel, fails fast if there are issues

Testing

CI pipeline runs on the branch.



Pull Request opened by Augment Code with guidance from the PR author


Note

Introduce a new ESLint workflow that runs before tests and remove legacy lint-report steps; add ESLint import exceptions for desktop server API imports.

  • CI:
    • New workflow: Add /.github/workflows/lint.yml running yarn lint.
    • Tests gating: In /.github/workflows/tests.yml, add lint job and require it for frontend-tests, backend-tests, and integration-tests.
    • Cleanup: Remove non-blocking “Code analysis” lint steps from tests-frontend.yml and tests-backend.yml.
  • Desktop:
    • Tweak redisinsight/desktop/src/lib/server/server.ts to disable import/extensions for api/dist imports to satisfy ESLint.

Written by Cursor Bugbot for commit e92effd. This will update automatically on new commits. Configure here.

- Add lint.yml reusable workflow that runs yarn lint
- Update tests.yml to call lint workflow first
- All test jobs now depend on lint passing
Add inline eslint-disable comments for imports from api/dist
which doesn't exist in CI (clean checkout without build artifacts).
Lint is now run as a blocking step before tests start,
making this Slack-reporting-only step redundant.
@github-actions
Copy link
Contributor

Code Coverage - Integration Tests

Status Category Percentage Covered / Total
🟢 Statements 81.5% 16343/20051
🟡 Branches 64.55% 7379/11430
🟡 Functions 70.4% 2289/3251
🟢 Lines 81.14% 15377/18950

@github-actions
Copy link
Contributor

Code Coverage - Frontend unit tests

St.
Category Percentage Covered / Total
🟢 Statements 82.86% 21099/25463
🟡 Branches 68.09% 8886/13051
🟡 Functions 78.05% 5783/7409
🟢 Lines 83.25% 20662/24818

Test suite run success

5487 tests passing in 704 suites.

Report generated by 🧪jest coverage report action from e92effd

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