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
* Add a documentation on how to contribute to the project
* add a docker compose example
* enhance copyright year
* new version, description of new variable MQTT_PASSWORD_FILE and more unit test documentation
* increase version
* fixing ruff command
* optimize code validation pipeline
* clean up requirements and optimize code test pipeline
* make python doc more useable, increase version, implement new feature to read mqtt password from file, clean up code in main block
- If using 3rd party components, the licence needs to be compatible with the license of this project
7
-
- Pull requests should describe the content of the code
8
-
- All pull request checks have to pass successfully
9
-
-
1
+
## How to contribute to weather2mqtt
2
+
3
+
#### **Did you find a bug?**
4
+
5
+
***Do not open up a GitHub issue if the bug is a security vulnerability
6
+
in weather2mqtt**, and instead write me a mail to [info@oberdorf-itc.de](mailto:info@oberdorf-itc.de).
7
+
8
+
***Ensure the bug was not already reported** by searching on GitHub under [Issues](https://github.com/cybcon/docker.weather2mqtt/issues).
9
+
10
+
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/cybcon/docker.weather2mqtt/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
11
+
12
+
#### **Did you write a patch that fixes a bug?**
13
+
14
+
* Open a new GitHub pull request with the patch.
15
+
16
+
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
17
+
18
+
* All commits needs to have a valid GPG signature
19
+
20
+
* All pull request checks have to pass successfully
21
+
22
+
* If using 3rd party components, the licence needs to be compatible with the license of this project
23
+
24
+
#### **Did you fix whitespace, format code, or make a purely cosmetic patch?**
25
+
26
+
Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the application will generally not be accepted.
27
+
28
+
#### **Do you intend to add a new feature or change an existing one?**
29
+
30
+
* Open a new GitHub pull request with the patch.
31
+
32
+
* Ensure the PR description clearly describes the new feature or the change. Include the relevant issue number if applicable.
33
+
34
+
* All commits needs to have a valid GPG signature
35
+
36
+
* All pull request checks have to pass successfully
37
+
38
+
* If using 3rd party components, the licence needs to be compatible with the license of this project
39
+
40
+
#### **Do you have questions about the source code?**
41
+
42
+
* Write me a mail to [info@oberdorf-itc.de](mailto:info@oberdorf-itc.de).
0 commit comments