Should this repo use pre-commit ot run linters, formatters, typo checkers, etc?

[cclauss]

Is your feature request related to a problem? Please describe.
I'm always frustrated when I push code changes, but the CI fails because of linter, formatter, or typo checks

Describe the solution you'd like
Perhaps we should consider running https://pre-commit.com/ and https://pre-commit.ci/ so that fast linting steps are done both locally on developers' machines and on GitHub CI. A pre-commit file might look something like:
https://raw.githubusercontent.com/ISKME/Open-Metadata-Exchange/refs/heads/main/.pre-commit-config.yaml

• [ci] - Add Ruff formatting step to CI pipeline #312 (comment)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Prek? It's written in Rust, much faster, and an alternative to pre-commit (Python).

This might be a bit too bleeding-edge compared to the broadly used and stable pre-commit, but I expect Prek will make more sense in the near future.

Additional context
Add any other context or screenshots about the feature request here.

@DhavalGojiya

[DhavalGojiya]

This might be a bit too bleeding-edge compared to the broadly used and stable pre-commit, but I expect Prek will make more sense in the near future.

Agreed - then we can go with pre-commit.

[cclauss]

Closed in:

• fix:add pre-commit #316

[tim-schilling]

@cclauss approved the request for the pre-commit CI github app. cc: @django-commons/admins