Repository navigation
docs: rules for publishers listing their own source and for agent-drafted PRs - #123
Merged
Merged
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.
Type
What
Two short CONTRIBUTING sections and one PR-template checkbox:
needs-review, list a free tier as the free tier only, record any in-tool upsell notice as a fact.npm testruns; name the fixed issue; a PR that records licences the author did not read is closed.Why
PR #78 was a publisher-submitted entry (disclosed in the PR, but no rule said to) and PR #122 came from an automated pipeline with a test file that CI never ran. Neither case is covered in the contributor docs today.
Checks
node site/validate.mjspasses (it checks the relative links in both files).🤖 Generated with Claude Code