docs: document CLI write support for content verification#563
Merged
torimwhaley merged 2 commits intomainfrom Apr 23, 2026
Merged
docs: document CLI write support for content verification#563torimwhaley merged 2 commits intomainfrom
torimwhaley merged 2 commits intomainfrom
Conversation
Update verified-content.mdx to remove the read-only caveat and document the new `verified: boolean` field with three-state semantics (true/false/absent), permissions behavior, and example workflow. Add `verification` and `verified` fields to both YAML examples in dashboards-as-code.mdx so the canonical YAML reference reflects what users will see after `lightdash download`. Pairs with lightdash#22139. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pairs with lightdash#22139, which adds a writable
verified: booleanfield to chart and dashboard YAML so users can verify/unverify content vialightdash upload.guides/verified-content.mdx— replaces the "currently read-only" Note callout with full documentation of the new write capability:verificationaudit block from the new writableverifiedbooleanlightdash downloadtrue/false/ absent)manage:ContentVerification)guides/developer/dashboards-as-code.mdx— addsverificationandverifiedfields to both YAML reference examples (dashboard and chart) with inline comments cross-linking to the verification guide. This way agents and skills reading the canonical YAML reference will see the verification fields as part of the standard structure.Hold for merge
Don't merge this until lightdash#22139 is merged and released, otherwise the docs will claim a feature that isn't shipped.
Test plan
/guides/verified-contentcross-link fromdashboards-as-code.mdxresolvestrue,false, absent) match the actual CLI behavior described in lightdash#22139 once that PR is merged🤖 Generated with Claude Code