A pre-commit hook for Ruff. Contribute to astral-sh/ruff-pre-commit development by creating an account on GitHub.

April 30, 2025 - 🔄 Seamless workflow: Fixes applied automatically during git commit ... repos: - repo: https://github.com/astral-sh/ruff-pre-commit # Ruff version. rev: v0.11.7 hooks: # Run the formatter.

- repo: https://github.com/astral-sh/ruff-pre-commit # Ruff version. rev: v0.15.17 hooks: # Run the linter. - id: ruff-check types_or: [ python, pyi ] args: [ --fix ] # Run the formatter.

A pre-commit hook for Ruff. Contribute to astral-sh/ruff-pre-commit development by creating an account on GitHub.

entry: ruff check --force-exclude · language: python · types_or: [python, pyi, jupyter] args: [] require_serial: true · additional_dependencies: [] minimum_pre_commit_version: "2.9.2" · - id: ruff-format · name: ruff format · description: "Run 'ruff format' for extremely fast Python formatting" entry: ruff format --force-exclude ·

ruff: This hook runs the Ruff linter with the --fix option to automatically fix issues in scripts and notebooks and a custom configuration file. ... This repository contains a mirror of mypy for pre-commit.

September 19, 2024 - Dear Foundry community & Palantir engineers Through our CI/CD pipelines we want to implement a way to automatically ensure that all PRs are following a defined code formatting principle. We are interrested to implement a code formatting and check through Ruff.

repos: - repo: https://github.com/nholuongut/ruff-pre-commit.git # Ruff version. rev: v0.7.0 hooks: # Run the linter. - id: ruff # Run the formatter.

- repo: https://github.com/astral-sh/ruff-pre-commit · rev: v0.15.15 · hooks: - id: ruff-format · name: mdtest format · types_or: [markdown] files: '^crates/.*/resources/mdtest/.*\.md$' pass_filenames: true ·

May 13, 2024 - After some searching, I found that you could sort the imports with ruff as follows [1]: ... Looks good! I’d have liked to have one command instead of two, and it would have been nice if I didn’t need to run check with a specific rule selected, but hey, this is still pretty easy to do. The only thing left was to figure out how to cajole it to a pre-commit hook.

January 1, 2025 - We have created a project with fully configured pre-commit hooks that check code quality and run tests for both the backend and frontend. This project can be used with any Python framework (Django, Flask, FastAPI) and JavaScript/TypeScript frameworks (ReactJS, VueJS, Angular, Svelte). You may need to make minor adjustments to the configuration to suit your specific needs. Additionally, you can modify and fine-tune the configurations for Ruff, MyPy, Prettier, and ESLint as you like since they offer great flexibility in customization.

This tutorial has focused on Ruff's command-line interface, but Ruff can also be used as a pre-commit hook via ruff-pre-commit:

November 23, 2023 - Ruff with all-in-one linting/formatting/analyzing and Pre-Commit with

December 7, 2025 - Example configuration for ruff (lines 1-14), ruff-format (lines 15-18), and numpydoc-validation (lines 20-37) pre-commit hooks in the pyproject.toml file.

IMPORTANT: PRs without the template ... PR adds ruff into the pyproject.toml and runs it in the quick-test workflow. It also adds support for hatch and some convenience scripts for developers. Additionally the linter and formatter get run before commits, using pre-commit Template Before submitting ...

Setting force-exclude = true will cause Ruff to respect these exclusions unequivocally. This is useful for pre-commit, which explicitly passes all changed files to the ruff-pre-commit plugin, regardless of whether they're marked as excluded by Ruff's own settings.

Ruff, the powerful Rust-based linter, has a formatter that is designed with the help of some of the Black authors to look 99.9% like Black, but run 30x faster. Here is the snippet to add the formatter to your .pre-commit-config.yml (combine with the Ruff linter below):

March 24, 2025 - Check ruff..............................................................Passed Check ruff-format......................................................Passed · If any errors exist, pre-commit will report them, and in some cases, Ruff will automatically fix the issues.

Top tips: * Have your 'pep8' target (and any other linter-related target run 'pre-commit' rather than the linters themselves), and don't forget to remove linters from test-requirements.txt once you do (with the exception of hacking if you have custom hacking rules) * Consider using ruff and ruff-format in place of all non-hacking linters/formatters: it's seriously fast and provides rules to cover most of these.