Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 2.23 KB

CONTRIBUTING.rst

File metadata and controls

49 lines (35 loc) · 2.23 KB

Contributing to Ray

Reporting bugs and asking questions

You can post questions or issues or feedback through the following channels:

  1. Discourse forum: For discussions about development and questions about usage.
  2. GitHub Issues: For bug reports and feature requests.
  3. StackOverflow

Finding issues to work on

We use GitHub labels to categorize issues and help contributors find work that matches their interests. See What can I work on? for a list of labels by component and type.

To contribute a patch:

We welcome contributions! See Getting Involved. To set up your development environment, see the Setting up your development environment section.

PR Review Process

For contributors who are in the ray-project organization:

  • When you first create a PR, add a reviewer to the assignee section.
  • Assignees will review your PR and add @author-action-required label if further actions are required.
  • Address their comments and remove @author-action-required label from the PR.
  • Repeat this process until assignees approve your PR.
  • Once the PR is approved, the author is in charge of ensuring the PR passes the build. Add test-ok label if the build succeeds.
  • Committers will merge the PR once the build is passing.

For contributors who are not in the ray-project organization:

  • Your PRs will have assignees shortly. Assignees or PRs will be actively engaging with contributors to merge the PR.
  • Please actively ping assignees after you address your comments!