You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
32 lines
1.4 KiB
32 lines
1.4 KiB
## Proposed change
|
|
|
|
<!--
|
|
Please include a summary of the change. Screenshots and/or videos can also be helpful if appropriate.
|
|
|
|
*** Please see the development guidelines for new widgets: https://gethomepage.dev/more/development/#service-widget-guidelines
|
|
*** If you do not follow these guidelines your PR will likely be closed without review.
|
|
|
|
New service widgets should include example(s) of relevant API output as well as updates to the docs for the new widget.
|
|
-->
|
|
|
|
Closes # (issue)
|
|
|
|
## Type of change
|
|
|
|
<!--
|
|
What type of change does your PR introduce to Homepage?
|
|
-->
|
|
|
|
- [ ] New service widget
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
- [ ] Documentation only
|
|
- [ ] Other (please explain)
|
|
|
|
## Checklist:
|
|
|
|
- [ ] If applicable, I have added corresponding documentation changes.
|
|
- [ ] If applicable, I have reviewed the [feature](https://gethomepage.dev/more/development/#new-feature-guidelines) and / or [service widget guidelines](https://gethomepage.dev/more/development/#service-widget-guidelines).
|
|
- [ ] I have checked that all code style checks pass using [pre-commit hooks](https://gethomepage.dev/more/development/#code-formatting-with-pre-commit-hooks) and [linting checks](https://gethomepage.dev/more/development/#code-linting).
|
|
- [ ] If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
|