mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
93f640751b
We require DCO in the PR, but people always forget it until the PR being created. Putting a prompt line in the PR template may help.
22 lines
993 B
Markdown
22 lines
993 B
Markdown
<!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. -->
|
|
|
|
<!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. -->
|
|
|
|
## Why are these changes needed?
|
|
|
|
<!-- Please give a short summary of the change and the problem this solves. -->
|
|
|
|
## Related issue number
|
|
|
|
<!-- For example: "Closes #1234" -->
|
|
|
|
## Checks
|
|
|
|
- [ ] I've signed off every commit(by using the -s flag, i.e., `git commit -s`) in this PR.
|
|
- [ ] I've run `scripts/format.sh` to lint the changes in this PR.
|
|
- [ ] I've included any doc changes needed for https://docs.ray.io/en/master/.
|
|
- [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
|
|
- Testing Strategy
|
|
- [ ] Unit tests
|
|
- [ ] Release tests
|
|
- [ ] This PR is not tested :(
|