| 1 |
<!-- |
| 2 |
⚡️ katchow! We ❤️ Pull Requests! |
| 3 |
|
| 4 |
If you remove or skip this template, you'll make the 🐼 sad and the mighty god |
| 5 |
of Github will appear and pile-drive the close button from a great height |
| 6 |
while making animal noises. |
| 7 |
|
| 8 |
Pull Request Requirements: |
| 9 |
* Please include tests to illustrate the problem this PR resolves. |
| 10 |
* Please lint your changes by running `npm run lint` before creating a PR. |
| 11 |
* Please update the documentation in `/docs` where necessary |
| 12 |
|
| 13 |
Please place an x (no spaces - [x]) in all [ ] that apply. |
| 14 |
--> |
| 15 |
|
| 16 |
<!-- the plugin(s) this PR is for --> |
| 17 |
|
| 18 |
## Rollup Plugin Name: `{name}` |
| 19 |
|
| 20 |
This PR contains: |
| 21 |
|
| 22 |
- [ ] bugfix |
| 23 |
- [ ] feature |
| 24 |
- [ ] refactor |
| 25 |
- [ ] documentation |
| 26 |
- [ ] other |
| 27 |
|
| 28 |
Are tests included? |
| 29 |
|
| 30 |
- [ ] yes (_bugfixes and features will not be merged without tests_) |
| 31 |
- [ ] no |
| 32 |
|
| 33 |
Breaking Changes? |
| 34 |
|
| 35 |
- [ ] yes (_breaking changes will not be merged unless absolutely necessary_) |
| 36 |
- [ ] no |
| 37 |
|
| 38 |
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking. |
| 39 |
|
| 40 |
List any relevant issue numbers: |
| 41 |
|
| 42 |
<!-- |
| 43 |
If this PR resolves any issues, list them as |
| 44 |
|
| 45 |
resolves #1234 |
| 46 |
|
| 47 |
where 1234 is the issue number. This will help us with house-keeping as Github will automatically add a note to those issues stating that a potential fix exists. Once the PR is merged, Github will automatically close those issues. |
| 48 |
|
| 49 |
If an issue is only solved partially or is relevant in some other way, just list the number without "resolves". |
| 50 |
--> |
| 51 |
|
| 52 |
### Description |
| 53 |
|
| 54 |
<!-- |
| 55 |
Please be thorough and clearly explain the problem being solved. |
| 56 |
* If this PR adds a feature, look for previous discussion on the feature by searching the issues first. |
| 57 |
* Is this PR related to an issue? |
| 58 |
--> |