docs: public-OSS no-downstream-references rule#4302
Conversation
|
Warning Review limit reached
More reviews will be available in 59 minutes and 34 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a hard documentation rule to keep this public OSS repository free of downstream-consumer-identifying references, aligning contributor/agent behavior with open-source constraints.
Changes:
- Introduces a “PUBLIC OSS repo — no downstream references” policy section in
CLAUDE.md. - Specifies prohibited downstream-consumer-identifying details (names/domains/infra/business decisions/private trackers) across code and collaboration artifacts.
|
|
||
| ## 🔓 PUBLIC OSS repo — no downstream references | ||
|
|
||
| This repository is open source. **Never reference downstream consumers** — project names, domains, cluster/infra details, business decisions, or links to private trackers — in code, comments, docs, issues, PRs, or commit messages. Use neutral wording ("a downstream consumer", "downstream rollouts"). Downstream-specific operations are tracked on the consumer's own repo, never here. |
Same rule as the Node twin PR: this public OSS repo must never reference its downstream consumers. Adds the hard rule to CLAUDE.md (agents + contributors). Historical mentions tracked in a follow-up issue. Docs only.