You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding a pre-commit config file would be good for formatting/linting purposes. I am currently working on a python CLI project myself and we use pre commit hooks for the above mentioned reason. In the config file we can define the usage of black, flake8 and isort. Even later on you can add a lint test as a GHA which would be great for new PRs.
Restart triage: P2 — consolidate local developer checks with #196. No pre-commit configuration is present in the inspected tree. Adding black, flake8, isort and pylint separately risks overlapping policies and avoidable churn.
Next step: agree on one formatter/linter policy, use matching versions/settings locally and in CI, and keep the initial change small. The deterministic test gate in #50 comes first.
Configuration review only; no formatting or lint commands were run. Keeping the issue open.
Activity
github-actions commentedon May 25, 2023
Hi👋 thanks for creating your first issue for IOSF, Will get back to you soon !.
GouravSardana commentedon Oct 21, 2026
Restart triage: P2 — consolidate local developer checks with #196. No pre-commit configuration is present in the inspected tree. Adding black, flake8, isort and pylint separately risks overlapping policies and avoidable churn.
Next step: agree on one formatter/linter policy, use matching versions/settings locally and in CI, and keep the initial change small. The deterministic test gate in #50 comes first.
Configuration review only; no formatting or lint commands were run. Keeping the issue open.