|
| 1 | +Provide a general summary of your changes in the Title above. |
| 2 | + |
| 3 | +## Description |
| 4 | + |
| 5 | +Describe your changes in detail. |
| 6 | + |
| 7 | +## Motivation, Context and link to the ticket |
| 8 | + |
| 9 | +- Why is this change required? What does it do? |
| 10 | +- If it fixes an open issue, please link to the issue here. |
| 11 | + |
| 12 | +## Related PRs |
| 13 | + |
| 14 | +Link to related pull requests. |
| 15 | + |
| 16 | +## How Has This Been Tested? |
| 17 | + |
| 18 | +- Please describe in detail how you tested your changes. |
| 19 | +- Include details of your testing environment, and the tests you ran to |
| 20 | +- see how your change affects other areas of the code, etc. |
| 21 | + |
| 22 | +## Screenshots (if appropriate): |
| 23 | + |
| 24 | +## Type of change |
| 25 | + |
| 26 | +What types of changes does your code introduce? Put an `x` in all the boxes that apply: |
| 27 | + |
| 28 | +- [ ] Update to existing guideline(s) |
| 29 | +- [ ] New guideline(s) |
| 30 | +- [ ] Miscellaneous change |
| 31 | +- [ ] Docusaurus updates (new plugins, bug fix, etc.) |
| 32 | + |
| 33 | +## Checklist: |
| 34 | + |
| 35 | +Go over all the following points, and put an `x` in all the boxes that apply. |
| 36 | +If you're unsure about any of these, don't hesitate to ask. Your team members are there to help! |
| 37 | + |
| 38 | +- [ ] My code follows the code style of this project. |
| 39 | +- [ ] My change requires a change to the documentation. |
| 40 | +- [ ] I have updated the documentation accordingly. |
| 41 | +- [ ] I have read the **CONTRIBUTING** document (if applicable) |
| 42 | +- [ ] I have added tests to cover my changes. |
| 43 | + - [ ] OR no tests update required. |
| 44 | +- [ ] One or more required reviews requested. |
0 commit comments