Repository navigation
Conversation
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.
Summary
~~~fenced example can contain H2 text without adding a PR section.zendev-lab/zendevand the supportedzendev-message-checkentry. Pin the hook and both PR actions to the same upstream revision.pnpm-workspace.yamlin the documented Cloudflare build watch paths for all three Workers.Validation
prek run --all-filesand the installed commit hook pass, including actionlint, Markdown/TOML checks, links, and workspace Astro checks.~~~fence passes; a body missing required Validation and Notes sections fails.Notes
Depends on #14. Shared validation is pinned to
7d8bcbf6134f62b7c7eaadb763f9a0d434717c44; v0.4.0 still fails the fenced-heading case. The English PR template remains the body contract.Cross-repository migration: zrr.dev #85 uses the same pinned upstream validation revision.