Skip to content
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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct __init__ filename in publish instructions #599

Merged
merged 3 commits into from
Dec 9, 2024
Merged

Correct __init__ filename in publish instructions #599

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bbe7175
Correct __init__ filename in publish instructions
richo Nov 27, 2024
efa3625
Also include hacs.json while spelling out repo format
richo Nov 27, 2024
be7eb91
Merge branch 'main' into patch-1
ludeeus Dec 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions source/docs/publish/integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
richo marked this conversation as resolved.
Show resolved Hide resolved
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._
Expand Down