From 87d57aa7a015507e5c2628a6380704c8036a5bd5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?rich=C3=B6=20butts?= Date: Mon, 9 Dec 2024 04:53:51 -0800 Subject: [PATCH] Correct __init__ filename in publish instructions (#599) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Correct __init__ filename in publish instructions * Also include hacs.json while spelling out repo format --------- Co-authored-by: Joakim Sørensen --- source/docs/publish/integration.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/source/docs/publish/integration.md b/source/docs/publish/integration.md index 278105dc..a816fd1e 100644 --- a/source/docs/publish/integration.md +++ b/source/docs/publish/integration.md @@ -17,28 +17,31 @@ For an integration repository to be valid, it must meet the requirements below. #### OK example: ``` -custom_components/awesome/__init_.py +custom_components/awesome/__init__.py custom_components/awesome/sensor.py custom_components/awesome/manifest.json README.md +hacs.json ``` #### Not OK example (1): ``` -awesome/__init_.py +awesome/__init__.py awesome/sensor.py awesome/manifest.json +awesome/hacs.json README.md ``` #### Not OK example (2): ``` -__init_.py +__init__.py sensor.py manifest.json README.md +hacs.json ``` _if you have `content_in_root` set to `true` in [`hacs.json`](start.md#hacsjson) this is valid._