|
| 1 | +## What does this PR do? |
| 2 | + |
| 3 | +<!-- |
| 4 | +Please include a summary of the change and which issue is fixed. |
| 5 | +Please also include relevant motivation and context. |
| 6 | +List any dependencies that are required for this change. |
| 7 | +
|
| 8 | +If we didn't discuss your PR in Github issues there's a high chance it will not be merged. |
| 9 | +
|
| 10 | +The following links the related issue to the PR (https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword) |
| 11 | +--> |
| 12 | + |
| 13 | +Fixes #\<issue_number> |
| 14 | + |
| 15 | +### Does your PR introduce any breaking changes? If yes, please list them. |
| 16 | + |
| 17 | +<!-- FILL IN or None --> |
| 18 | + |
| 19 | +## Before submitting |
| 20 | + |
| 21 | +- [ ] Was this **discussed/approved** via a GitHub issue? (not for typos and docs) |
| 22 | +- [ ] Did you read the [contributor guideline](https://github.com/Lightning-AI/lightning/blob/master/.github/CONTRIBUTING.md), **Pull Request** section? |
| 23 | +- [ ] Did you make sure your **PR does only one thing**, instead of bundling different changes together? |
| 24 | +- [ ] Did you make sure to **update the documentation** with your changes? (if necessary) |
| 25 | +- [ ] Did you list all the **breaking changes** introduced by this pull request? |
| 26 | + |
| 27 | +<!-- In the CHANGELOG, separate each item in the unreleased section by a blank line to reduce collisions --> |
| 28 | + |
| 29 | +## PR review |
| 30 | + |
| 31 | +Anyone in the community is welcome to review the PR. |
| 32 | +Before you start reviewing, make sure you have read the [review guidelines](https://github.com/Lightning-AI/lightning/wiki/Review-guidelines). In short, see the following bullet-list: |
| 33 | + |
| 34 | +- [ ] Is this pull request ready for review? (if not, please submit in draft mode) |
| 35 | +- [ ] Check that all items from **Before submitting** are resolved |
| 36 | +- [ ] Make sure the title is self-explanatory and the description concisely explains the PR |
| 37 | +- [ ] Add labels and milestones (and optionally projects) to the PR so it can be classified |
0 commit comments