[DNM] Gree Integration rewrite

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,56 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
+title: 'Bug: '
 labels: ''
 assignees: ''
 
 ---
 
 **Describe the bug**
+
 A clear and concise description of what the bug is.
 
 **To Reproduce**
-Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
 
-**Configuration**
-Share your YAML here
-
 **Expected behavior**
+
 A clear and concise description of what you expected to happen.
 
 **Screenshots**
+
 If applicable, add screenshots to help explain your problem.
 
-**Platform:**
- - OS: [e.g. HASSIO, Hassbian]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 0.92.1]
+**Runtime Information:**
 
+ - OS: [e.g. HASSIO, Hassbian, Docker]
+ - Home Assistant Version: [e.g. 2026.4]
+ - Integration Version: [e.g. 0.92.1]
+ - Device Firmware Version: [e.g. 1.44]
+ - Device model: [e.g., Gree GWH12ACC-K6DNA1D]
+ - Does the device respond to pings? Yes/No
+
 **Additional context**
+
 Add any other context about the problem here.
 
+**Configuration**
+
+Share your configuration entry diagnostics download or YAML here
+
+```json
+Paste the diagnostics json here
+```
+
+```yaml
+If applicable, paste the config here
+```
+
 **Logs**
-Please share your Home Assistant logs here. Make sure to remove any personal/secret information.
+
+Please share your Home Assistant logs here. Make sure to remove any personal/secret information. See [here](https://github.com/p-monteiro/HomeAssistant-GreeClimateComponent-Rewrite/tree/gree-rewrite?tab=readme-ov-file#debugging).

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,7 +1,7 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
+title: 'Feature Request: '
 labels: ''
 assignees: ''
 

.github/workflows/validate.yaml

@@ -0,0 +1,34 @@
+name: Validate
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - master
+      - 4.0-pre-release
+  pull_request:
+    branches:
+      - master
+      - 4.0-pre-release
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  hassfest: # https://developers.home-assistant.io/blog/2020/04/16/hassfest/
+    name: Hassfest validation
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout the repository
+        uses: "actions/checkout@v6"
+
+      - name: Run hassfest validation
+        uses: home-assistant/actions/hassfest@master
+
+  hacs: # https://github.com/hacs/action
+    name: HACS validation
+    runs-on: ubuntu-latest
+    steps:
+      - name: Run HACS validation
+        uses: hacs/action@22.5.0
+        with:
+          category: integration

CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing
+
+This integration follows the development guidelines for Home Assistant integrations, while keeping the repository compatible with HACS.
+
+## Development Environment
+
+Home Assistant provides [several guidelines](https://developers.home-assistant.io/docs/development_environment) regarding the setup of the development environment. Because we are not contributing to the official integrations, there is no need to fork the official [Home Assistant Core](https://github.com/home-assistant/core) repository. However, it is useful to use it as it provides a preconfigured VSCode development environment with the necessary tools.
+
+Here's a general guide to get it working with this integration repository:
+
+1. Create a folder for the development (for example `development/`)
+2. Clone [home-assistant/core ](https://github.com/home-assistant/core) inside of it (`development/core`)
+3. Follow the [guidelines](https://developers.home-assistant.io/docs/development_environment) on getting the devcontainer working
+4. Fork [this](https://github.com/RobHofmann/HomeAssistant-GreeClimateComponent) repository and clone your fork inside of the same folder (`development/YourForkName`)
+5. Create a branch for your changes in the cloned repo `git checkout -b my-branch-name`
+6. Create a mount point for this integration in the devcontainer
+    1. Open `development/core/devcontainer/devcontainer.json`
+    2. Add the mounting:
+	```json
+		"mounts": [
+			"source=${localWorkspaceFolder}/../YourForkName/custom_components/gree_custom,target=/workspaces/core/config/custom_components/gree_custom,type=bind"
+		],
+	```
+7. Open `development/core` with VSCode
+8. Use the command **"Dev Containers: Reopen in Container"**
+9. Once inside the container make sure the folder `config/custom_components/gree_custom` exists
+10. You should be now be able to edit the integration files from inside the devcontainer
+11. Make your changes
+12. Push to your fork, rebase with the latest upstream version and submit a pull request
+
+## Testing
+
+Use the **Run Home Assistant Core** Task to start Home Assistant.
+
+You should also be able to set and hit breakpoints in your code.
+
+If you change your code, you have to restart Home Assistant (rerun the Task)
+
+## Styling
+
+Please adhere to the recomended coding style: https://developers.home-assistant.io/docs/development_guidelines

LICENSE

@@ -1,7 +1,7 @@
                     GNU GENERAL PUBLIC LICENSE
                        Version 3, 29 June 2007
 
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 
@@ -645,7 +645,7 @@ the "copyright" line and a pointer to where the full notice is found.
     GNU General Public License for more details.
 
     You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
 
 Also add information on how to contact you by electronic and paper mail.
 
@@ -664,11 +664,11 @@ might be different; for a GUI interface, you would use an "about box".
   You should also get your employer (if you work as a programmer) or school,
 if any, to sign a "copyright disclaimer" for the program, if necessary.
 For more information on this, and how to apply and follow the GNU GPL, see
-<http://www.gnu.org/licenses/>.
+<https://www.gnu.org/licenses/>.
 
   The GNU General Public License does not permit incorporating your program
 into proprietary programs.  If your program is a subroutine library, you
 may consider it more useful to permit linking proprietary applications with
 the library.  If this is what you want to do, use the GNU Lesser General
 Public License instead of this License.  But first, please read
-<http://www.gnu.org/philosophy/why-not-lgpl.html>.
+<https://www.gnu.org/licenses/why-not-lgpl.html>.