How to run pre-commit inside folder

Hi! I have project structure like this

.
├── README.md
├── backend
│   ├── Pipfile
│   ├── Pipfile.lock
│   ├── mypy.ini
│   ├── pylintrc
│   ├── pyproject.toml
│   ├── src
│   ├── tests
│   └── tox.ini
├── docker
│   ├── backend
│   └── postgres
├── docker-compose.yml
└── .pre-commit-config.yaml

I would like to run pre-commit’s flake8 inside backend folder, how could I achieve this?

Issue Analytics

State:
Created 4 years ago
Reactions:6
Comments:25 (9 by maintainers)

Top GitHub Comments

4reactions

sjdemartinicommented, Dec 18, 2020

For anyone who comes across this later, I based my approach on what patrick91 did (thanks for the tips!), but noticed that the approach with entry: bash -c 'cd ... && ... "$@"' (i.e., passing the file names along with bash via $@) actually ends up dropping the first filename and doesn’t send the complete list. For me, rather than:

entry: bash -c 'cd frontend && yarn precommit-lint "$@"'

This worked instead:

entry: yarn --cwd frontend precommit-lint

4reactions

patrick91commented, Aug 28, 2019

@asottile I had to do something a bit hacky to support entry: bash -c 'cd ... && ... "$@"'. My use case is that I want to use eslint without having to install dependencies twice, I’m also running in a monorepo setup, similar to the one in the first comment. We have a frontend folder with all the configuration for eslint and running eslint from outside the frontend folder has been a bit tricky, for example it would ignore the .eslintignore file. Also using the bash hack didn’t work as pre-commit passes the path with frontend/, so the file wasn’t being found. For now I’ve solved using a custom script that fixes the paths, but I don’t really like it 😃

Do you have a better suggestion?

Here’s the hack I did, for more context: https://github.com/pythonitalia/pycon/pull/808/commits/f623cf87bc235bcfab07fbad0eed7d119fa971e1