|
| 1 | +<!-- |
| 2 | + You are amazing! Thanks for contributing to our project! |
| 3 | + Please fill the template to help maintainers processing your PR. |
| 4 | +
|
| 5 | + Don't forget to create the PR against the correct branch: |
| 6 | + - new product id -> new_product_ids |
| 7 | + - anything else -> dev |
| 8 | +--> |
| 9 | +## Context |
| 10 | +<!-- |
| 11 | + Summarize the motivation and context of the change. |
| 12 | + Which issue are you dealing with? |
| 13 | +--> |
| 14 | + |
| 15 | + |
| 16 | +## Proposed change |
| 17 | +<!-- |
| 18 | + Describe the change. How are you fixing the issue? |
| 19 | +--> |
| 20 | + |
| 21 | + |
| 22 | +## Type of change |
| 23 | +<!-- |
| 24 | + What type of change does your PR introduce? |
| 25 | + Please, check only 1 box! |
| 26 | +--> |
| 27 | + |
| 28 | +- [ ] Dependency upgrade |
| 29 | +- [ ] Bugfix (non-breaking change which fixes an issue) |
| 30 | +- [ ] New device |
| 31 | +- [ ] New product id (the device is already supported with a different id) |
| 32 | +- [ ] New feature (which adds functionality to an existing device) |
| 33 | +- [ ] Breaking change (fix/feature causing existing functionality to break) |
| 34 | +- [ ] Code quality improvements to existing code or addition of tests |
| 35 | +- [ ] Documentation |
| 36 | + |
| 37 | +## Additional information |
| 38 | +<!-- |
| 39 | + Link docs and related issues, when applicable. |
| 40 | +--> |
| 41 | + |
| 42 | +- This PR fixes issue: fixes # |
| 43 | +- This PR is related to: |
| 44 | +- Link to documentation pull request: |
| 45 | + |
| 46 | +## Checklist |
| 47 | +<!-- |
| 48 | + Please do your best to check these boxes. |
| 49 | +--> |
| 50 | + |
| 51 | +- [ ] The code change is tested and works locally. |
| 52 | +- [ ] The code has been formatted using Black. |
| 53 | +- [ ] The code follows the [Zen of Python](https://www.python.org/dev/peps/pep-0020/). |
| 54 | +- [ ] I am creating the Pull Request against the correct branch. |
| 55 | +- [ ] Documentation added/updated. |
0 commit comments