Skip to content

[Feature] Modernise pre-commit tools and their settings #449

Open

Description

@IgorTatarnikov
No description provided.

Activity

  1. alessandrofelder commented on Jul 24, 2026

    @alessandrofelder
    Member

    Moved to org-wide issue for discussion

    Cross-linking all the pre-commit - updating-related issues here, as they seem a bit scattered: https://github.com/search?q=org%3Abrainglobe+pre-commit++&type=issues&state=open , and so hopefully we can close many of those once we address this.

    We should agree on the setting first (I don't think we have, @AlgoFoe @brainglobe/active-devs ), before we do a sweep on all repos.
    (I thought we had started this discussion elsewhere, but I may have imagined this 😬 please cross-link if this was real 😂 ).

    As far as can remember, we agreed to:
    * use ruff as far as possible for linting, and make the settings
    * mirror the set-up in movement for consistency (as far as it makes sense for BrainGlobe).
    * use the same standard in all repos (currently varies by repo).
    * maybe codespell

    Did we agree on what type checker to use?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions