Allow docs-only PRs without validation sections #73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
allod change submitstill hard-requires every PR body to include a## Validationsection:That now conflicts with the Allod memory guidance being added in allod/memory#6: docs-only PRs do not need validation sections unless a command checks a real failure mode, and agents should avoid process-noise comments when there are no findings worth sharing.
Update
allod change submitso routine documentation-only PRs can be submitted without a fake validation section. The implementation should also update the submit tests intests/allod-change.sh, which currently assert that missing validation is always rejected, including dry-run mode.Possible implementation approaches:
--docs-onlyor--no-validation-required;The important contract is that
allod change submitshould not force meaningless validation boilerplate for docs-only PRs, while still preserving useful validation requirements for code, generated artifacts, provisioning behavior, and other executable changes.After implementing the
--docs-onlyflag initially proposed here, we reconsidered whether the validation check itself is worth keeping. Thebody_has_validation_headingcheck is a syntactic gate that can't verify quality — agents can trivially satisfy it with boilerplate. The real forcing function is agent memory guidance, which can apply judgment about when a validation section is meaningful.Rather than adding a flag to work around a check that wasn't pulling its weight, PR #74 removes the validation enforcement entirely: deletes
body_has_validation_heading, the--docs-onlyflag, and all related tests. Net -44 lines, no new options.The
## Validationconvention for code PRs continues to be guided by agent memory, where it belongs.