Skip to content

[Trivial] clarify strict-mode warning error wording - #6899

Closed
lennartkats-db wants to merge 4 commits into
databricks:mainfrom
lennartkats-db:fix/strict-mode-warning-wording
Closed

lennartkats-db wants to merge 4 commits into
databricks:mainfrom
lennartkats-db:fix/strict-mode-warning-wording

Conversation

@lennartkats-db

@lennartkats-db lennartkats-db commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

Changes

Clarify that bundle validate --strict treats warnings as errors. Update the acceptance snapshots.

Why

Matches the existing --strict help and Clang's wording for the same behavior.

Tests

  • Targeted acceptance cases and ./task checks pass.
  • Full ./task test fails in unrelated bundle/scripts, libs/dyn/jsonloader, and libs/exec tests. Lint panics in buildir; fmt cannot fetch Ruff.

This PR was written by Codex.

@github-actions github-actions Bot added the DABs DABs related issues label Oct 1, 2026
@lennartkats-db lennartkats-db changed the title Clarify strict-mode warning error wording [Trivial] clarify strict-mode warning error wording Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

An authorized user can trigger integration tests manually by following the instructions below:

Trigger:
go/deco-tests-run/cli

Inputs:

  • PR number: 6899
  • Commit SHA: f7e6a14feb726974a6858dc4ae1f15e007e05dd4

Checks will be approved automatically on success.

@lennartkats-db

Copy link
Copy Markdown
Contributor Author

Superseded by #6916, which uses a branch in databricks/cli so the build can access its OIDC token.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

DABs DABs related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant