Link to the documentation on contributing from CONTRIBUTING.rst (#19396)

Co-authored-by: Richard Liaw <rliaw@berkeley.edu>
This commit is contained in:
iasoon 2021-11-16 00:34:18 +01:00 committed by GitHub
parent ec81f52061
commit 171ad62e30
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -15,6 +15,30 @@ To contribute a patch:
We welcome your contribution! Please see https://docs.ray.io/en/master/getting-involved.html for instructions.
For instructions on setting up your development environment, check out the
`getting involved`_ documentation page.
.. _`Github Discussions`: https://github.com/ray-project/ray/discussions
.. _`GitHub Issues`: https://github.com/ray-project/ray/issues
.. _`StackOverflow`: https://stackoverflow.com/questions/tagged/ray
.. _`getting involved`: https://docs.ray.io/en/master/getting-involved.html
PR Review Process
-----------------
For contributors who are in the ray-project organization:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- When you first create a PR, add an 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!