-
Notifications
You must be signed in to change notification settings - Fork 58
docs(#3344): add "Why Conforma?" documentation page#3349
Open
fullsend-ai-coder[bot] wants to merge 1 commit into
Open
docs(#3344): add "Why Conforma?" documentation page #3349fullsend-ai-coder[bot] wants to merge 1 commit into
fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
Add a new documentation page explaining the value proposition of using Conforma (EC) over cosign directly. The page covers six key areas: policy-as-code evaluation with OPA/Rego, batch and snapshot validation, structured output and reporting (JSON, YAML, JUnit, VSA, etc.), EnterpriseContractPolicy CRD integration, Tekton task integration, and the built-in rule library. The page is linked from the main navigation and the index page. Closes #3344
🤖 Finished Review · ✅ Success · Started 10:27 AM UTC · Completed 10:37 AM UTC
Commit: 47d3320 · View workflow run →
Review
Findings
Low
- [naming-conventions]
docs/modules/ROOT/pages/why-conforma.adoc:1— The new document filename uses kebab-case (why-conforma.adoc). Among auto-generated CLI docs, underscores dominate (ec_validate_image.adoc), but among manually authored multi-word pages, kebab-case is actually the more common pattern (6 files vs 2). This is consistent with the existing convention and no change is needed.
Info
- [sub-agent-failure]
N/A— The challenger sub-agent returned an empty adjudicated findings set after removing the single low finding with evidence. Falling back to the pre-challenger finding set per process. The challenger's evidence was sound: kebab-case is the dominant convention for hand-authored multi-word documentation pages in this repo.
@@ -0,0 +1,95 @@
= Why Conforma?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[low] naming-conventions
The new document filename uses kebab-case (why-conforma.adoc). Among manually authored multi-word filenames in the pages directory, kebab-case (6 files) outnumbers underscore-case (2 files) by 3:1. The ec_* underscore files are auto-generated from CLI subcommand names. This file follows the dominant convention for hand-authored documentation pages — no change needed.
@fullsend-ai-review
fullsend-ai-review
Bot
added
the
ready-for-merge
All reviewers approved — ready to merge
label
Jun 19, 2026
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
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
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.
Add a new documentation page explaining the value proposition of using Conforma (EC) over cosign directly. The page covers six key areas: policy-as-code evaluation with OPA/Rego, batch and snapshot validation, structured output and reporting (JSON, YAML, JUnit, VSA, etc.), EnterpriseContractPolicy CRD integration, Tekton task integration, and the built-in rule library.
The page is linked from the main navigation and the index page.
Closes #3344
Post-script verification
agent/3344-why-conforma-docs)15814bf9896060ce26a127adc995a1fbb60c3a77..HEAD)