isort skipping everything in CI (Bitbucket pipelines) with absolute filepath with default settings

[fohrloop]

I'm running isort as a part of another script which calls isort and gives an absolute path to it. After some time debugging why isort works locally but not in pipelines I found out that isort by default skips any folders with "build" and Bitbucket pipelines runs the CI pipelines inside a folder called /opt/atlassian/pipelines/agent/build (which ends in "build").

+ python -m isort /opt/atlassian/pipelines/agent/build --profile black --filter-files --check-only --verbose

                 _                 _
                (_) ___  ___  _ __| |_
                | |/ _/ / _ \/ '__  _/
                | |\__ \/\_\/| |  | |_
                |_|\___/\___/\_/   \_/

      isort your imports, so you don't have to.

                    VERSION 5.13.2

/opt/atlassian/pipelines/agent/build was skipped as it's listed in 'skip' setting, matches a glob in 'skip_glob' setting, or is in a https://bitbucket.org/vaisala-ds/wxh-analytics/src/5b9364249b0c9897220eb0aab60e06b928f3dff0/.gitignore file with --skip-gitignore enabled.
Skipped 1 files

The config indeed has "build" in the "skip":

$ python -m isort --show-config | grep build -C 10
    "py_version": "py3",
    "force_to_top": [],
    "skip": [
        "node_modules",
        ".tox",
        ".nox",
        ".eggs",
        ".mypy_cache",
        "buck-out",
        ".hg",
        "build",
        "__pypackages__",
        ".pants.d",
        ".direnv",
        ".svn",
        "dist",
        "venv",
        "_build",
        ".venv",
        ".bzr",
        ".git",
        ".pytype"
    ],

which are coming from the "defaults":

            "source": "defaults"

From isort help I can see the following target options:

target options:
  files                 One or more Python source files that need their imports sorted.
  --filter-files        Tells isort to filter files even when they are explicitly passed in as part of the CLI command.
  -s SKIP, --skip SKIP  Files that isort should skip over. If you want to skip multiple files you should specify twice: --skip file1 --skip file2. Values can be file names,
                        directory names or file paths. To skip all files in a nested path use --skip-glob.
  --extend-skip EXTEND_SKIP
                        Extends --skip to add additional files that isort should skip over. If you want to skip multiple files you should specify twice: --skip file1 --skip file2.
                        Values can be file names, directory names or file paths. To skip all files in a nested path use --skip-glob.
  --sg SKIP_GLOB, --skip-glob SKIP_GLOB
                        Files that isort should skip over.
  --extend-skip-glob EXTEND_SKIP_GLOB
                        Additional files that isort should skip over (extending --skip-glob).
  --gitignore, --skip-gitignore
                        Treat project as a git repository and ignore files listed in .gitignore. NOTE: This requires git to be installed and accessible from the same shell as isort.
  --ext SUPPORTED_EXTENSIONS, --extension SUPPORTED_EXTENSIONS, --supported-extension SUPPORTED_EXTENSIONS
                        Specifies what extensions isort can be run against.
  --blocked-extension BLOCKED_EXTENSIONS
                        Specifies what extensions isort can never be run against.
  --dont-follow-links   Tells isort not to follow symlinks that are encountered when running recursively.
  --filename FILENAME   Provide the filename associated with a stream.
  --allow-root          Tells isort not to treat / specially, allowing it to be run against the root dir.

but is there other way to "skip the skip", other than masking it with nonexistent folder name, like

python -m isort /opt/atlassian/pipelines/agent/build --profile black --filter-files --check-only --skip nonexistent-folder-just-to-make-isort-work-in-bitbucket

?

[fohrloop]

And of course I found the solution the minute I post this.

The problem was the --filter-files

  --filter-files        Tells isort to filter files even when they are explicitly passed in as part of the CLI command.