Repository navigation
Add CONTRIBUTING.md linking to the Playground handbook - #4288
Conversation
Add CONTRIBUTING.md with setup, conventions, and PR guidelines The repo has no root-level CONTRIBUTING.md; contributor info is scattered across the README, the docs site, and AGENTS.md. This consolidates fork/clone/build steps, coding and testing conventions, the PR and GPL licensing process, and links to the existing docs pages into one file GitHub surfaces automatically when someone opens an issue or PR.
Add a root-level CONTRIBUTING.md so GitHub surfaces contributor guidance automatically on new issues and PRs. It gives a short summary of the ways to contribute (code, docs, translations, triage, ideas) and links each one out to the corresponding page in the Playground Handbook (developer.wordpress.org/playground/handbook/contributing/), along with the Code of Conduct and GPL licensing terms.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughAdded ChangesContributor Documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This documentation-only change adds contributor guidance without affecting product behavior or production systems. No actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Motivation for the change, related issues
Implementation details
Testing Instructions (or ideally a Blueprint)
Summary by CodeRabbit