Skip to content

ci(lint): set LINT_ERROR_THRESHOLD to zero#238

Merged
balazs-szucs merged 1 commit into
grimmory-tools:developfrom
peterfortuin:chore/lint-threshold-to-zero
Mar 27, 2026
Merged

ci(lint): set LINT_ERROR_THRESHOLD to zero#238
balazs-szucs merged 1 commit into
grimmory-tools:developfrom
peterfortuin:chore/lint-threshold-to-zero

Conversation

@peterfortuin

@peterfortuin peterfortuin commented Mar 27, 2026

Copy link
Copy Markdown
Contributor

Description

Since all the lint issue are solved, we need set the threshold to zero.

Linked Issue: #133

Changes

This pull request makes a small configuration change to the linting workflow. The error threshold for linting has been set to zero, which means any lint error will now cause the workflow to fail.

Summary by CodeRabbit

  • Chores
    • Strengthened the lint quality gate to enforce stricter error thresholds in the build pipeline. This ensures higher code quality standards are maintained across the project.

@coderabbitai

coderabbitai Bot commented Mar 27, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The LINT_ERROR_THRESHOLD environment variable in the Angular lint workflow was changed from 721 to 0, making the lint quality gate stricter to fail whenever any lint errors are present instead of allowing up to 721 errors.

Changes

Cohort / File(s) Summary
Workflow Configuration
.github/workflows/angular-lint-threshold.yml
Changed LINT_ERROR_THRESHOLD from 721 to 0, tightening the lint error quality gate to fail on any lint errors.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

chore

Suggested reviewers

  • balazs-szucs

Poem

🐰 With a flick of my whiskers and a hop so fine,
The threshold has shifted from 721 to the line,
No lints shall pass through our quality gate,
Zero errors now—nothing but great! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description includes all required sections from the template (Description, Linked Issue, Changes) with relevant details about the configuration change and its rationale.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The PR title follows the conventional commit format with type 'ci' and scope 'lint', accurately describing the main change of setting LINT_ERROR_THRESHOLD to zero.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
✨ Simplify code
  • Create PR with simplified code

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot added the chore label Mar 27, 2026
@imnotjames

Copy link
Copy Markdown
Contributor

I think this should be ci(lint): set LINT_ERROR_THRESHOLD to zero if following conventional commits.

@peterfortuin peterfortuin changed the title chore(lint): set LINT_ERROR_THRESHOLD to zero ci(lint): set LINT_ERROR_THRESHOLD to zero Mar 27, 2026
@peterfortuin

Copy link
Copy Markdown
Contributor Author

I think this should be ci(lint): set LINT_ERROR_THRESHOLD to zero if following conventional commits.

Done

@balazs-szucs balazs-szucs left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@balazs-szucs balazs-szucs merged commit fea9cfb into grimmory-tools:develop Mar 27, 2026
15 checks passed
@peterfortuin peterfortuin deleted the chore/lint-threshold-to-zero branch March 27, 2026 18:33
zachyale pushed a commit to zachyale/grimmory that referenced this pull request Apr 17, 2026
zachyale pushed a commit to zachyale/grimmory that referenced this pull request Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants