Conversation
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
WalkthroughThis PR contains minor infrastructure and documentation updates: updating the Pagefind binary download source in the Dockerfile, correcting documentation links and terminology in component guides, updating repository references from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
content/components/sensor/xiaomi_ble.md (1)
13-13: Legacy{{< docref >}}shortcode on changed line.Per coding guidelines,
{{< docref >}}is legacy and should be replaced with a standard Markdown link. Since this line was modified in this PR, it's a good opportunity to update it. That said, the entire file uses this shortcode extensively, so a bulk migration might be better suited for a separate PR.Example replacement for this line
- You may alternatively use ESPHome's {{< docref "/components/bluetooth_proxy" >}} component to forward sensor data to Home Assistant and have Mijia devices configured using its own Mijia BLE component. + You may alternatively use ESPHome's [Bluetooth Proxy](/components/bluetooth_proxy) component to forward sensor data to Home Assistant and have Mijia devices configured using its own Mijia BLE component.As per coding guidelines:
**/*.md: Hugo shortcode{{< docref >}}is legacy and should be replaced with standard Markdown links.
Description:
This PR updates some GitHub URLs in the documentation
Checklist:
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/components/_index.mdwhen creating new documents for new components or cookbook.New Component Images
If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.
To generate a component image:
Comment on this pull request with the following command, replacing
component_namewith your component name in lower_case format with underscores (e.g.,bme280,sht3x,dallas_temp):The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.
Extract the SVG file and place it in the
/static/images/folder of this repository.Use the image in your component's index table entry in
/components/_index.md.Example: For a component called "DHT22 Temperature Sensor", use: