Skip to content

Clarify that --exclude replaces the default exclusion list - #541

Merged
Halleck45 merged 1 commit into
masterfrom
exclude_vendor_warning
Aug 2, 2026
Merged

Clarify that --exclude replaces the default exclusion list#541
Halleck45 merged 1 commit into
masterfrom
exclude_vendor_warning

Conversation

@Halleck45

@Halleck45 Halleck45 commented Jul 29, 2026

Copy link
Copy Markdown
Collaborator

The --exclude option replaces the default exclusion list instead of extending it. This is intended, but easy to miss: a custom exclusion list silently brings vendor code into the analysis, which inflates metrics such as LOC (see #364).

Capture d’écran du 2026-07-29 07-25-50

The --exclude option replaces the default exclusion list instead of
extending it. This is intended, but easy to miss: a custom exclusion
list silently brings vendor code into the analysis, which inflates
metrics such as LOC (see #364).

- document the behavior and the default list in the --help output;
- display an orange warning when a custom exclusion list does not
  contain "vendor" while a vendor directory is present in the
  analyzed directories.
@Halleck45
Halleck45 force-pushed the exclude_vendor_warning branch from e812e2f to ad9fd27 Compare July 29, 2026 05:43
@Halleck45
Halleck45 merged commit f4a9a3b into master Aug 2, 2026
12 checks passed
@Halleck45
Halleck45 deleted the exclude_vendor_warning branch August 2, 2026 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant