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: CONTRIBUTING.md
+42-36Lines changed: 42 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,39 +23,45 @@ Pull requests are the best way to propose changes to the codebase.
23
23
24
24
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
25
25
26
-
## Report bugs using Github's [issues](../../issues)
27
-
28
-
GitHub issues are used to track public bugs.
29
-
Report a bug by [opening a new issue](../../issues/new/choose); it's that easy!
30
-
31
-
## Write bug reports with detail, background, and sample code
32
-
33
-
**Great Bug Reports** tend to have:
34
-
35
-
- A quick summary and/or background
36
-
- Steps to reproduce
37
-
- Be specific!
38
-
- Give sample code if you can.
39
-
- What you expected would happen
40
-
- What actually happens
41
-
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
42
-
43
-
People *love* thorough bug reports. I'm not even kidding.
44
-
45
-
## Use a Consistent Coding Style
46
-
47
-
Use [black](https://github.com/ambv/black) to make sure the code follows the style.
48
-
49
-
## Test your code modification
50
-
51
-
This custom component is based on [panda_status template](https://github.com/ping-localhost/panda-status).
52
-
53
-
It comes with development environment in a container, easy to launch
54
-
if you use Visual Studio Code. With this container you will have a stand alone
55
-
Home Assistant instance running and already configured with the included
By contributing, you agree that your contributions will be licensed under its MIT License.
26
+
## Development
27
+
28
+
The easiest way to get started with development is to use Visual Studio Code with [devcontainers](https://code.visualstudio.com/docs/devcontainers/containers). This approach creates a preconfigured development environment with the necessary tools
29
+
30
+
You can follow the [official Home Assistant guide](https://developers.home-assistant.io/docs/setup_devcontainer_environment/) for the initial setup.
31
+
32
+
Below is a single, consolidated version of the two text fragments, with consistent structure, corrected numbering, and the repository URL set to `https://github.com/ping-localhost/panda-status`.
33
+
34
+
### Getting ready
35
+
36
+
1. Clone the repository to a local directory on your computer:
Copy file name to clipboardExpand all lines: README.md
-43Lines changed: 0 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,49 +77,6 @@ After installation, add the integration via Home Assistant UI:
77
77
78
78
For issues or feature requests, open an [issue on GitHub](https://github.com/ping-localhost/panda-status/issues).
79
79
80
-
## Development
81
-
82
-
The easiest way to get started with development is to use Visual Studio Code with [devcontainers](https://code.visualstudio.com/docs/devcontainers/containers). This approach creates a preconfigured development environment with the necessary tools
83
-
84
-
You can follow the [official Home Assistant guide](https://developers.home-assistant.io/docs/setup_devcontainer_environment/) for the initial setup.
85
-
86
-
Below is a single, consolidated version of the two text fragments, with consistent structure, corrected numbering, and the repository URL set to `https://github.com/ping-localhost/panda-status`.
87
-
88
-
### Getting ready
89
-
90
-
1. Clone the repository to a local directory on your computer:
0 commit comments