astral-sh/ruff - CodSpeed

ruff

Blog Docs Changelog

Performance History

Latest Results

Use internal Salsa APIs to make it compile

micha/salsa-db-key

2 hours ago

micha/try-salsa-update

2 hours ago

[ty] Reduce monomorphization (#22195)

main

3 hours ago

[ty] Fix playground inlay hint location (#22200)

main

4 hours ago

internal lint.tab-size is the indent-width setting

brent/document-options

13 hours ago

Document more rules with options Summary -- While analyzing our rules, I wanted to know which of them use configuration options but noticed that some of them were not documented (or at least not documented in a separate `## Options` section). I had Claude generate an initial list of candidate rules, but it contained a lot of false positives that I filtered out, and I ended up adding all of these sections myself. I'm not claiming that the options lists are exhaustive (as in the rules may use additional options beyond what I found), but this will at least help with my goal of determining whether or not a rule is configurable at all and also hopefully be helpful in general. I mostly just tacked on an `## Options` section without any commentary, but I added a couple lines of explanation when I felt it wasn't obvious from the context. I also noticed a bit of variation in the `flake8-simplify` rules from doing this. Some of them offer a diagnostic but no fix depending on the resulting line length of the suggestion, while others offer neither. I'm not sure we need to do anything different here, but it seemed worth mentioning. Test Plan -- Docs tests to make sure the links are right

brent/document-options

13 hours ago

[ty] Automatically re-run ecosystem-analyzer workflow on subsequent pushes to a PR, if the PR has the `ecosystem-analyzer` label (#22179) ## Summary This PR reworks our ecosystem-analyzer workflow so that it automatically reruns if a PR with the `ecosystem-analyzer` label has new commits pushed to it, or is reopened after previously being closed. It's currently easy to forget that you need to remove and re-add the label to trigger a fresh workflow run, which can then mean that there are stale (misleading) results in the PR comment posted by the bot. It also means that it takes longer for CI to finish than it would otherwise, because it might be a few minutes after pushing new commits to the PR before you remember that you also need to remove and re-add the label. To write this PR, I consulted: - The GitHub workflow trigger documentation: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request - This Stack Overflow answer: https://stackoverflow.com/a/59588725/13990016 ## Test Plan I experimented with pushing commits to this PR and closing/reopening it, and both of these actions triggered fresh runs of the ecosystem-analyzer worfklow when the label was present on the PR. However, removing the label again meant that the workflow was no longer triggered by these actions.

main

18 hours ago

[ty] Split out `ty_python_types` crate

micha/ty-python-types

19 hours ago

Active Branches

[ty] Test performance and memory impact of shrinking Salsa's DB key

last run

2 hours ago

+1%

Document more rules with options

last run

13 hours ago

0%

[ty] Split out `ty_python_types` crate

last run

19 hours ago

-5%

© 2025 CodSpeed Technology

Home Terms Privacy Docs