Skip to content

docs: rules for publishers listing their own source and for agent-drafted PRs - #123

Merged
TMHSDigital merged 1 commit into
mainfrom
docs/contributor-disclosure
Oct 22, 2026
Merged

TMHSDigital merged 1 commit into
mainfrom
docs/contributor-disclosure

Conversation

@TMHSDigital

Copy link
Copy Markdown
Owner

Type

  • Docs or site

What

Two short CONTRIBUTING sections and one PR-template checkbox:

  • Submitting your own source: publishers may list their own work; say so in the PR, write the entry as a third party would (no comparisons with other entries), start at needs-review, list a free tier as the free tier only, record any in-tool upsell notice as a fact.
  • Automated and AI-assisted pull requests: judged on the diff; keep tests in the two files npm test runs; 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.mjs passes (it checks the relative links in both files).

🤖 Generated with Claude Code

…fted PRs

Two gaps surfaced by PRs #78 (publisher-submitted entry) and #122
(automated PR with an unwired test file). CONTRIBUTING gains a section on
each; the PR template gains one checkbox covering both.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@TMHSDigital
TMHSDigital merged commit 5e064fc into main Oct 22, 2026
3 checks passed
@TMHSDigital
TMHSDigital deleted the docs/contributor-disclosure branch October 22, 2026 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant