You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ body:
21
21
required: true
22
22
- label: This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
23
23
required: true
24
-
- label: This issue is not a duplicate issue of any [previous issues](https://github.com/ludeeus/integration_blueprint/issues?q=is%3Aissue+label%3A%22Bug%22+)..
24
+
- label: This issue is not a duplicate issue of any [previous issues](https://github.com/ping-localhost/panda_status/issues?q=is%3Aissue+label%3A%22Bug%22+)..
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ body:
13
13
required: true
14
14
- label: This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
15
15
required: true
16
-
- label: This issue is not a duplicate feature request of [previous feature requests](https://github.com/ludeeus/integration_blueprint/issues?q=is%3Aissue+label%3A%22Feature+Request%22+).
16
+
- label: This issue is not a duplicate feature request of [previous feature requests](https://github.com/ping-localhost/panda_status/issues?q=is%3Aissue+label%3A%22Feature+Request%22+).
The component and platforms in this repository are not meant to be used by a
4
-
user, but as a "blueprint" that custom component developers can build
5
-
upon, to make more awesome stuff.
6
-
7
-
HAVE FUN! 😎
8
-
9
-
## Why?
10
-
11
-
This is simple, by having custom_components look (README + structure) the same
12
-
it is easier for developers to help each other and for users to start using them.
13
-
14
-
If you are a developer and you want to add things to this "blueprint" that you think more
15
-
developers will have use for, please open a PR to add it :)
3
+
Control your BigTreeTech Panda Status via Home Assistant.
16
4
17
5
## What?
18
6
@@ -22,25 +10,8 @@ File | Purpose | Documentation
22
10
-- | -- | --
23
11
`.devcontainer.json` | Used for development/testing with Visual Studio Code. | [Documentation](https://code.visualstudio.com/docs/remote/containers)
24
12
`.github/ISSUE_TEMPLATE/*.yml` | Templates for the issue tracker | [Documentation](https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository)
25
-
`custom_components/integration_blueprint/*` | Integration files, this is where everything happens. | [Documentation](https://developers.home-assistant.io/docs/creating_component_index)
13
+
`custom_components/panda_status/*` | Integration files, this is where everything happens. | [Documentation](https://developers.home-assistant.io/docs/creating_component_index)
26
14
`CONTRIBUTING.md` | Guidelines on how to contribute. | [Documentation](https://help.github.com/en/github/building-a-strong-community/setting-guidelines-for-repository-contributors)
27
15
`LICENSE` | The license file for the project. | [Documentation](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository)
28
16
`README.md` | The file you are reading now, should contain info about the integration, installation and configuration instructions. | [Documentation](https://help.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax)
29
17
`requirements.txt` | Python packages used for development/lint/testing this integration. | [Documentation](https://pip.pypa.io/en/stable/user_guide/#requirements-files)
30
-
31
-
## How?
32
-
33
-
1. Create a new repository in GitHub, using this repository as a template by clicking the "Use this template" button in the GitHub UI.
34
-
1. Open your new repository in Visual Studio Code devcontainer (Preferably with the "`Dev Containers: Clone Repository in Named Container Volume...`" option).
35
-
1. Rename all instances of the `integration_blueprint` to `custom_components/<your_integration_domain>` (e.g. `custom_components/awesome_integration`).
36
-
1. Rename all instances of the `Integration Blueprint` to `<Your Integration Name>` (e.g. `Awesome Integration`).
37
-
1. Run the `scripts/develop` to start HA and test out your new integration.
38
-
39
-
## Next steps
40
-
41
-
These are some next steps you may want to look into:
42
-
- Add tests to your integration, [`pytest-homeassistant-custom-component`](https://github.com/MatthewFlamm/pytest-homeassistant-custom-component) can help you get started.
43
-
- Add brand images (logo/icon) to https://github.com/home-assistant/brands.
44
-
- Create your first release.
45
-
- Share your integration on the [Home Assistant Forum](https://community.home-assistant.io/).
46
-
- Submit your integration to [HACS](https://hacs.xyz/docs/publish/start).
0 commit comments