Ignore formatting a nested folder

[SadmiB]

I'm trying black formatter github actions and I want to ignore formatting a nested folder, the documentation says that the --exclude accepts a regex but it didn't worked, I tested both regex and text as input.

Example of the tests I did:

name: Lint

on: [push, pull_request]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-python@v2
      - uses: psf/black@stable
        with:
          args: ". --check --exclude /(folder1/folder2)/"

I tested many other combinations too, but the directory is always included. is this a bug or I'm missing something(the documentation is not concentrated on the github action)?

[ichard26]

The last time I checked our path normalization code, those /s shouldn't matter? but it's worth trying out.

[SadmiB]

actually I inspired it from readme, since it says the default is /(\.direnv|\.eggs|\.git|\. hg|\.mypy_cache|\.nox|\.tox|\.venv|\.svn|_bu ild|buck-out|build|dist)/, but this still just a test of many combinations I tried, how could I ignore a folder?

[ichard26]

Hmm, what's the (or relevant bits of the) folder structure of the project?

[SadmiB]

I have inside folder1 a library that I don't want to format, let's say it's folder2. and I want to ignore folder1/folder2 for being formatted.
I hope this what your question was about.

[ichard26]

The reason why I ask is because maybe there is a slight difference that is affecting whether the regex matches or not. A basic reproduction case doesn't work locally:

ichard26@acer-ubuntu:~/testing$ tree 
.
└── folder1
    ├── a.py
    ├── b.py
    └── folder2
        ├── a.py
        └── b.py

2 directories, 4 files
ichard26@acer-ubuntu:~/testing$ black . -v --exclude "/(folder1/folder2)/"
folder1/folder2 ignored: matches the --exclude regular expression
/home/ichard26/testing/folder1/a.py already well formatted, good job.
/home/ichard26/testing/folder1/b.py already well formatted, good job.
All done! ✨ 🍰 ✨
2 files left unchanged.

[SadmiB]

Yes, as I mentioned in the issue above I'm facing this with black github actions. I'm getting exactly the same result as you above locally.

the reason why all this started is that folder2 is actually a darknet library and when formatting it it returns an error, and there is no reason it should be formatted, so I decided to ignore it, but that won't happen with the github actions.

[ichard26]

Maybe try black_args: instead of args: ? (imo it's dumb that our action uses that as its input name, but I haven't been involved in its addition)

YEAH DON'T DO THAT CAUSE THAT CHANGE ONLY HAPPENED IN THE DEVELOPMENT BRANCH