[MNT] Update .gitignore
#1547
Merged
[MNT] Update .gitignore
#1547
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1547 +/- ##
===========================================
- Coverage 85.24% 64.23% -21.01%
===========================================
Files 38 36 -2
Lines 5008 4351 -657
===========================================
- Hits 4269 2795 -1474
- Misses 739 1556 +817 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fkiraly
approved these changes
Dec 30, 2025
fkiraly
pushed a commit
that referenced
this pull request
Jan 14, 2026
…ruff checks (#1553) #### Metadata * Stacks on #1547 (for ignoring `.ruff_cache`) * Reference Issue: fixes #1550 * New Tests Added: No * Documentation Updated: No #### Details What does this PR implement/fix? Explain your changes. * Updates the ruff version in .pre-commit-config.yaml to 0.14.10 * Runs `ruff format .` to align the codebase with the formatting rules of the updated Ruff version * Fixes also added to pass `ruff check .` checks * Add `noqa` tags in places that will end up changing the architecture of the function/class if I try fixing it * Only changes from my end to the actual code would be changing small things like: * the print statements to be compatible with check [UP031](https://docs.astral.sh/ruff/rules/printf-string-formatting/) * Changing variable names to `_` to be compatible with [RUF059](https://docs.astral.sh/ruff/rules/unused-unpacked-variable/) This PR is going to be a bigger one in size but in my opinion, we should be compatible with the latest ruff version and get it over with sooner rather than later. On a separate note, there are already a significant number of `noqa` tags in the codebase. We should consider revisiting the architecture of the functions and classes that rely on them to better align with Ruff’s best practices. Where alignment isn’t appropriate, we should at least discuss why those components don’t need to be Ruff-compatible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
.gitignoreto includepre-commitand cursor files #1546What does this PR implement/fix? Explain your changes.
.ruff_cacheto .gitignore.