Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.1k
[nrf52] Update mdns.md with 'See Also' section#5608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:next
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Added additional references to related components.
✅ Deploy Preview foresphome ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
As this is a feature matched with a PR inhttps://github.com/esphome/esphome, please target your PR to thenext branch and rebase.
netlifybot commentedNov 12, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview foresphome ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
Base branch has been corrected - dismissing previous review.
lboue commentedNov 12, 2025
@copilot I changed to next branch |
Uh oh!
There was an error while loading.Please reload this page.
Description:
Update mdns.md with 'See Also' section
Related issue (if applicable): fixes
Pull request inesphome with YAML changes (if applicable):
Checklist:
I am merging into
nextbecause this is new documentation that has a matching pull-request inesphome 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.rstwhen 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 inUPPER_CASE format withunderscores (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
images/folder of this repository.Use the image in your component's index table entry in
/components/index.rst.Example: For a component called "DHT22 Temperature Sensor", use: