|
| 1 | +## Description |
| 2 | +<!-- Describe your changes in detail --> |
| 3 | + |
| 4 | +## Motivation and context |
| 5 | +<!-- Why is this change required? What problem does it solve? --> |
| 6 | +<!-- If it fixes an open issue, please link the issue here. --> |
| 7 | + |
| 8 | +## How has this been tested? |
| 9 | +<!-- Please describe how you tested your changes. --> |
| 10 | + |
| 11 | +## Screenshots (if appropriate) |
| 12 | + |
| 13 | +## Types of changes |
| 14 | +<!-- What types of changes does your code introduce? --> |
| 15 | +<!-- Put an `x` in all the boxes that apply: --> |
| 16 | +- [ ] Bug fix (non-breaking change which fixes an issue) |
| 17 | +- [ ] New feature (non-breaking change which adds functionality) |
| 18 | +- [ ] Breaking change (fix or feature that would cause existing |
| 19 | +functionality to not work as before) |
| 20 | + |
| 21 | +## Checklist |
| 22 | +<!-- See the following points, and put an `x` in all the boxes that apply. --> |
| 23 | +<!-- If you're unsure about any of these, please ask. We're here to help! --> |
| 24 | +- [ ] PR title provides summary of the changes and starts with one of the |
| 25 | +[pre-defined prefixes](../../utils/release.yml) |
| 26 | +<!-- For example: "doc: Add example to db.describe documentation" --> |
| 27 | +<!-- or if it is a fix use "db.describe: fix JSON output format" --> |
| 28 | +- [ ] My code follows the [code style](../../doc/development/style_guide.md) |
| 29 | +of this project. |
| 30 | +- [ ] My change requires a change to the documentation. |
| 31 | +- [ ] I have updated the documentation accordingly. |
| 32 | +- [ ] I have added tests to cover my changes. |
0 commit comments