docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root#70
Conversation
14 packages carried their own copies — 6 divergent versions of the code of conduct and 12 of the contributing guide, all describing the old standalone-repo workflow (fork the package repo) that the read-only mirrors no longer support. Replace them with one of each at the monorepo root: the Contributor Covenant 2.1, and a contributing guide written for the monorepo workflow (bin/monorepo check/test/validate, linked testing, Vale). Package docs now link to the monorepo copies, since the mirrors no longer ship the files. The root CONTRIBUTING.md is ours rather than boilerplate, so it is no longer excluded from the Vale docs lint. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Benchmark resultshttp — Swoole modes (4 cores, 200 VUs, 20s/run)
a = HYPERLOOP_A (process), b = HYPERLOOP_B (coroutine) Shared CI runners — treat absolute numbers as rough, compare modes within a run. Commit 113b4ef. |
Greptile SummaryRemoves 14 divergent per-package
Confidence Score: 5/5Pure documentation reorganization with no logic changes — safe to merge. All per-package community health files are removed and every known link (READMEs, adapter guides, PR template) is updated to the monorepo-absolute URL. No relative links to the deleted files remain anywhere in the package tree, and the adapter guides' workflow steps now correctly describe the monorepo fork path end-to-end. No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "docs: point adapter guides at the monore..." | Re-trigger Greptile |
The storage and messaging adapter guides still told contributors to fork the read-only mirror and push there, contradicting the central CONTRIBUTING.md they now link to. Collapse the GitHub fork tutorial into a short monorepo-accurate prerequisites section, fix the raise-a-PR step, make source paths monorepo-relative, and run tests via bin/monorepo. Also fix the ambiguous 'Fork the project' line in the di and http READMEs, and the guide's copy-pasted 'Storage adapter name' in the messaging doc. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
What
Removes per-package
CODE_OF_CONDUCT.mdandCONTRIBUTING.md(and therefore from the mirrors) and replaces them with a single up-to-date copy of each at the monorepo root. Net: +86 / −2,642 lines.Why
14 packages carried their own copies — 6 divergent versions of the code of conduct and 12 divergent versions of the contributing guide. All of them described the old standalone-repo workflow ("fork the repository, push, open a PR") which the read-only mirrors no longer support, and some pointed contributors at mirror URLs or even
appwrite/appwrite's code of conduct.The central copies
CODE_OF_CONDUCT.md— Contributor Covenant, upgraded 2.0 → 2.1 (the old copies also had ateam@appwrite.io..typo).CONTRIBUTING.md— written for the monorepo workflow: where development happens,bin/monorepo check/test/validate,--linkedtesting, the Vale docs lint, PR and release conventions, and the security-report channel. Since it's now an authored doc rather than boilerplate, it's no longer excluded from the Vale lint (and passes).Link updates
All references now point at the monorepo copies, since the mirrors no longer ship the files: the
[contribution guide](CONTRIBUTING.md)links in package READMEs, absolute links to mirror repos (utopia-php/{di,storage,http,messaging}/blob/.../CONTRIBUTING.md), and the adapter-guide docs in storage/messaging that referenced../CODE_OF_CONDUCT.md.Follow-up idea (not in this PR)
An org-level
utopia-php/.githubrepository with default community health files would make GitHub surface the contributing guide and code of conduct on every mirror automatically, without shipping files in the splits.🤖 Generated with Claude Code