Exclusions

Exclusions describe files that no standard should measure. Use categories for semantic groups and paths for project-specific cases.

exclude:
  gitignored: true
  categories:
    - assets
    - configuration
    - documentation
    - generated
    - tests
    - vendored
    - dependencies
  paths:
    - src/generated/**

Built-in categories

Category	Purpose
`assets`	Static assets, images, fonts, PDFs, design files, audio, and video.
`configuration`	Tool and package configuration files whose shape is imposed by another system, such as package.json, tsconfig, go.mod, Cargo.toml, pyproject.toml, and .considered.yaml.
`documentation`	Repository prose such as README, changelog, docs directories, Markdown, text, reStructuredText, and AsciiDoc.
`generated`	Lockfiles, generated directories, codegen outputs, protobuf outputs, and generated filename suffixes.
`tests`	Conventional test files and directories from common language ecosystems and test runners.
`vendored`	Committed third-party source such as vendor, third_party, external, and vendored directories.
`dependencies`	Installed dependency directories such as node_modules, virtual environments, and package stores.

Paths

Custom paths use doublestar glob syntax. They are useful for local conventions that are meaningful to one repository but too specific for a built-in category.

GitHub Actions workflows are intentionally not part of theconfiguration category. They are YAML, but they often behave more like operational programs than static tool settings.