chore: run ruff only at the pre-commit stage #2900
Closed
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note sure if this affected anyone else, but I was getting duplicate ruff checks in the pre-commit hook.
Greptile Overview
Updated On: 2025-10-15 20:49:00 UTC
Greptile Summary
This PR addresses a pre-commit configuration issue where ruff code quality checks were running multiple times. The change restricts both
ruff-check
andruff-format
hooks to only execute during the pre-commit stage by addingstages: [pre-commit]
to both hooks in.pre-commit-config.yaml
. This follows the same pattern already used by the commitlint hook and prevents the duplicate execution that was causing the issue described in the PR. The change is minimal and targeted, affecting only the pre-commit hook configuration without impacting the actual code quality checks or formatting behavior.PR Description Notes:
Important Files Changed
Changed Files
Confidence score: 5/5