Configure pre-commit tool for this repo

[webknjaz]

Rules:

1. DO NOT commit to the main branch directly. ever.
2. ABSOLUTELY NO force pushes allowed for public non-feature branches.
3. For every feature, create a new branch matching name features/<issue-number>-<feature-name>.
4. Submit every feature by creating Pull Request @ github, after that wait for review, fix issues, repeat until approved. If needed rebase the branch on top of main and re-push force it.

• [ ] I HAVE READ AND UNDERSTOOD THE RULES ABOVE

• [x] Install pre-commit locally as follows:

  python3.11 -m pip install pre-commit --user
  python3.11 -m pre_commit install

• [x] Create branch called features/12-pre-commit-integration
• [x] Add .pre-commit-config.yaml config, containing the following hooks:
  • [x] no-commit-to-branch
  • [x] add-trailing-comma
  • [x] remove-tabs
  • [x] trailing-whitespace
  • [x] check-merge-conflict
  • [x] double-quote-string-fixer
  • [x] requirements-txt-fixer
  • [x] check-yaml
  • [x] check-docstring-first
  • [x] end-of-file-fixer
  • [x] name-tests-test
  • [x] check-ast
  • [x] debug-statements
  • [x] flake8
  • [x] pydocstyle
  • [x] pylint using "local" mode
  • [x] mypy
• [x] Check repo using command pre-commit run --all-files, fix all issues and commit fixes as well
• [x] Create PR with this branch

[Martolivna]

Should I write some commit description when adding a new configuration file?

[webknjaz]

A full commit message with title and description is almost always a good idea. Give it a try. If it turns out to not be compliant w/ #6 and #7, that can always be corrected during the PR review.