What breaks without openclaw contributing guide
Rejected PRs for missing tests. Wrong commit format. Skipped issue-first process.
→
Accepted first PR × documented contributor process ÷ 15-minute read ÷ no rejection cycles = merged contribution.
Security check — openclaw contributing guide
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm N/A — documentation only compatibility.
Quick start — openclaw contributing guide in 15 minutes to read
Setup time: 15 minutes to read
!
You need:
- Git
- GitHub account
- Node.js ≥18 for code contributions
Install the package:
# Development setup:
git clone https://github.com/openclaw/openclaw
cd openclaw && npm install
npm test
1
Read CONTRIBUTING.md in full
2
Find or file an issue for your contribution
5
Write code and tests following the style guide
6
Open a PR referencing the issue
Compatibility & status
Works with: N/A — documentation only
beginner
Last updated: Oct 2025
MIT
Official docs →
View on GitHub →
FAQ — openclaw contributing guide
Do I need to file an issue before opening a PR?
Yes for anything non-trivial. Small fixes (typos, docs) can go direct PR.
How long does PR review take?
The maintainers aim for first response within 5 business days.
Is there a contributor covenant or code of conduct?
Yes — linked from CONTRIBUTING.md.