Skip to content
View source on GitHub
Browse documentation

Use qualityGuide 06

Changed files and baselines

Keep local and pull-request feedback focused without hiding failures.

quality documentation View Markdown
On this page

Changed-file mode

Use --changed with checks, formatting, or fixes:

quality check --changed
quality check --changed origin/main
quality format --changed
quality fix --changed

In CI, reporting and failure thresholds can be tuned separately:

quality check --changed origin/main \
  --report-level warning \
  --fail-level error

Without a base, quality includes staged, unstaged, and untracked files. With a base, it also includes branch changes since that revision.

Configuration changes trigger the corresponding full analyzer because a rules change can affect files that were not edited. Project-wide analyzers also retain their required project scope.

Deleted paths participate in relevance checks. Deleting an analyzer configuration triggers a full run, and deleting a source file still triggers matching project-wide tasks and analyzers. File-scoped tools receive only paths that still exist, so a deleted file is never passed to an executable.

Renames include both the removed path and the new path, so moving a configuration file still triggers its full analyzer. Replacing a regular file with a symlink, or a symlink with a regular file, also counts as a changed input.

Paths beginning with a dash receive an explicit relative-path prefix before being passed as file arguments. The stable detekt CLI receives comma-separated inputs; filenames containing a comma trigger a complete project check because they cannot be represented unambiguously in that input list.

Adapter selection composes with changed-file mode:

quality check --changed origin/main --only eslint,astro-check
quality check --changed --only oxlint
quality format --changed --exclude swiftformat

Baseline an existing repository

Create a baseline after verifying every required tool is installed and runs successfully:

quality baseline create
git add .quality-baseline.json quality.yml

Existing matching findings are suppressed on later checks; new findings still fail.

Fingerprints exclude line and column positions, so moving code does not create noise. Duplicate occurrences are counted, which means adding another copy of an existing violation is still detected.

Safety rules

A baseline is refused when a required tool is missing, crashes, or returns output that cannot be fully parsed. Infrastructure failures must never become accepted code-quality debt.

Existing baselines also leave findings visible when a failed analyzer’s output cannot be fully parsed. A recorded warning cannot turn an execution failure into a passing check.

Failure thresholds apply to fully parsed findings. An unsuccessful analyzer with unrecognized output still fails when --fail-level error is selected.

Baseline creation accepts the same --jobs, --timeout-seconds, and --max-output-bytes controls as checks. Raise the capture limit when a structured report exceeds the default limit; incomplete findings must not become a baseline.