Add issue and PR templates

.github/ISSUE_TEMPLATE/1_bug_report_sdk.yaml

@@ -0,0 +1,41 @@
+name: 🐛 SDK bug report
+description: SDK bug report template
+labels: bug in SDK
+
+body:
+  - type: input
+    id: affected-versions
+    attributes:
+      label: version(s) affected
+      placeholder: x.y.z
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the problem in SDK
+    validations:
+      required: true
+  - type: textarea
+    id: how-to-reproduce
+    attributes:
+      label: How to reproduce
+      description: |
+        ⚠️  This is the most important part of the report ⚠️
+        Without a way to easily reproduce your issue, there is little chance we will be able to help you and work on a fix.
+        Please, take the time to show us some code and/or config that is needed for others to reproduce the problem easily.
+    validations:
+      required: true
+  - type: textarea
+    id: possible-solution
+    attributes:
+      label: Possible Solution
+      description: |
+        Optional: only if you have suggestions on a fix/reason for the bug
+        Don't hesitate to create a pull request with your solution, it helps get faster feedback.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: "Optional: any other context about the problem: log messages, screenshots, etc."

.github/ISSUE_TEMPLATE/2_feature_request_sdk.yaml

@@ -0,0 +1,17 @@
+name: 🚀 SDK Feature Request
+description: Ideas for new features and improvements in SDK
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the new feature
+    validations:
+      required: true
+  - type: textarea
+    id: example
+    attributes:
+      label: Example
+      description: |
+        A simple example of the new feature in action (include PHP code, YAML config, etc.)
+        If the new feature changes an existing feature, include a simple before/after comparison.

.github/ISSUE_TEMPLATE/3_bug_report_rest_api.yaml

@@ -0,0 +1,41 @@
+name: 🐛 REST-API bug report
+description: REST-API bug report template
+labels: bug in REST-API
+
+body:
+  - type: input
+    id: api-method
+    attributes:
+      label: REST-API method name
+      placeholder: user.current
+    validations:
+      required: true
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the problem in REST-API call
+    validations:
+      required: true
+  - type: textarea
+    id: how-to-reproduce
+    attributes:
+      label: How to reproduce
+      description: |
+        ⚠️  This is the most important part of the report ⚠️
+        Without a way to easily reproduce your issue, there is little chance we will be able to help you and work on a fix.
+        Please, take the time to show us some code and/or config that is needed for others to reproduce the problem easily.
+    validations:
+      required: true
+  - type: textarea
+    id: possible-solution
+    attributes:
+      label: Possible Solution
+      description: |
+        Optional: only if you have suggestions on a fix/reason for the bug
+        Don't hesitate to create a pull request with your solution, it helps get faster feedback.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: "Optional: any other context about the problem: log messages, screenshots, etc."

.github/ISSUE_TEMPLATE/4_feature_request_rest_api.yaml

@@ -0,0 +1,17 @@
+name: 🚀 REST-API Feature Request
+description: Ideas for new features and improvements in REST-API
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: A clear and concise description of the new feature
+    validations:
+      required: true
+  - type: textarea
+    id: example
+    attributes:
+      label: Example
+      description: |
+        A simple example of the new feature in action (include PHP code, YAML config, etc.)
+        If the new feature changes an existing feature, include a simple before/after comparison.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,16 @@
+| Q             | A                                                                                                                         |
+|---------------|---------------------------------------------------------------------------------------------------------------------------|
+| Bug fix?      | yes/no                                                                                                                    |
+| New feature?  | yes/no <!-- please update CHANGELOG.md file -->                                                                           |
+| Deprecations? | yes/no <!-- please update CHANGELOG.md file -->                                                                           |
+| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead --> |
+| License       | **MIT**                                                                                                                       |
+
+<!--
+Replace this notice by a description of your feature/bugfix.
+This will help reviewers and should be a good start for the documentation.
+
+Additionally:
+ - Always add tests and ensure they pass.
+ - For new features, provide some code snippets to help understand usage.
+-->