A distributed framework for scaling AI workloads and Python applications.
Ray puts contribution policy before setup. Contributors must check for duplicate work, remain accountable for the result, and provide local test evidence. Existing guides retain the build and style details.
├── ├── .claude │ └── · imports ../AGENTS.md ├── doc │ ├── .claude │ │ └── │ └── source │ └── ray-contribute │ ├── │ └── ├── python │ └── ray │ ├── data │ │ └── .claude │ │ └── │ ├── serve │ │ └── .claude │ │ └── │ ├── train │ │ └── .claude │ │ └── │ └── tune │ └── .claude │ └── ├── rllib │ └── .claude │ └── ├── src │ └── ray │ └── .claude │ └── └──
01 / Contribution etiquette
The opening connects a PR to notifications, CI runs, and reviewer attention. That rationale frames the later restrictions on duplicate work and mass-generated cleanup.
Source excerpt starting at line 6.Ray is a high-traffic repository. Every PR notifies CODEOWNERS, triggers CI, andconsumes maintainer attention. Automated, low-value, or duplicate contributions
02 / Hard prohibitions
Duplicate work, trivial busywork, and changes that a human cannot test or defend are separate reasons not to open a PR. The fallback is a short explanation of what is missing.
Source excerpt starting at line 51.If the requested work is a duplicate, trivial busywork, or cannot be tested anddefended by a human, **do not open a PR**. Return a short explanation of what ismissing instead.
03 / Contribution etiquette
The description must establish that the work is distinct, identify test commands and outcomes, and disclose assistance. These requirements complement the instruction that the human review every changed line.
Source excerpt starting at line 44.- PR descriptions for AI-assisted work **must** state: - Why this is not duplicating an existing issue or PR. - The test commands run and their results. - That AI assistance was used.
04 / Pointing at the source of truth
The root gives a short project layout and test timeout, then links to setup, build, and contribution documents. Detailed command guidance remains with those existing sources.
Source excerpt starting at line 65.The default test timeout is 180s (`pytest.ini`). For build, test, lint, andcode-style details, follow Ray's existing guides rather than duplicating themhere:
These instructions explain how to work in Ray. Modem shows your agents what customers said, who is affected, and what changed.