Skip to content

feat: Write suppressions to default file#19

Merged
danthompson merged 2 commits into
mainfrom
feat/write-suppressions-default-file
May 12, 2026
Merged

feat: Write suppressions to default file#19
danthompson merged 2 commits into
mainfrom
feat/write-suppressions-default-file

Conversation

@danthompson
Copy link
Copy Markdown
Member

  • --write-suppressions (bare) writes .dbt-lint-suppressions.yml next to your config, or in cwd if no config is discovered.
  • --write-suppressions=PATH writes to an explicit path; --write-suppressions=- writes to stdout (unchanged from prior behavior).
  • File writes overwrite without prompt and emit Wrote N suppressions to <path> to stderr; the = form is required when the option precedes the manifest positional.

--write-suppressions becomes an optional-value flag with three modes:
bare writes .dbt-lint-suppressions.yml next to your config (or in cwd
if none); =PATH writes to that path; =- writes to stdout.

File writes overwrite without prompt and emit a confirmation to
stderr ("Wrote N suppressions to <path>"). Stdout mode is unchanged.
Use =, not a space, since the flag takes an optional value.
Earlier copy said "Use =, not a space" as a flat rule. The actual
constraint is narrower: the bare form must be placed last on the
command line so Click doesn't consume the manifest path as the
option's value. The =PATH and =- forms can appear in any position,
including with a space separator.
@danthompson danthompson marked this pull request as ready for review May 12, 2026 13:19
@danthompson danthompson merged commit ef7de42 into main May 12, 2026
5 checks passed
@danthompson danthompson deleted the feat/write-suppressions-default-file branch May 12, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant