Add Pre-commit Hooks for Code Formatting and Linting #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses closes #77 by adding pre-commit hooks to automatically handle code formatting and linting for various file types in the repository. These hooks help maintain consistent code style and formatting across Python files, Jupyter Notebooks, YAML, Markdown, and text files, ensuring better code quality and minimizing errors before committing.
Changes:
.pre-commit-config.yaml
file to configure the pre-commit hooks..ipynb
).Key Updates:
nbQA
.check-yaml
hook.mdformat
(replacing markdownlint).Notes:
markdownlint
due to Ruby dependency issues and replaced it with a Python-based Markdown formatter (mdformat
) to avoid Ruby-related setup complications.nbqa-flake8
where necessary to avoid common linting errors (e.g., long lines, unused imports).How to Test:
This ensures that all files are formatted and linted according to the new configuration, improving code quality across the repository.