Merge branch 'develop' into update/assign-update-product-author-from-…

…rest-api

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,54 @@
+name: Bug Report
+description: File a bug report
+labels: ["bug", "triage"]
+projects: ["dokan-plugin"]
+assignees:
+  - dokan
+body:
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Bug Description
+      description: In a few sentences or paragraphs, describe the bug in detail. Include information such as what the bug does, what was expected, steps to reproduce the bug, any error messages, and the impact of the bug on the application.
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Step To Reproduce
+      description: List step-by-step instructions to reproduce the bug. This helps the assigned team member understand and replicate the issue.
+      value: |
+        1. Go to '...'
+        2. Click on '....'
+        3. Scroll down to '....'
+        4. See error
+  - type: textarea
+    id: logs2
+    attributes:
+      label: Expected Behaviour
+      description: Describe what you expected to happen when performing the steps listed above.
+    validations:
+      required: true
+  - type: textarea
+    id: logs3
+    attributes:
+      label: Actual Behaviour
+      description: Describe what actually happened when performing the steps, highlighting the bug's behavior.
+    validations:
+      required: true
+  - type: textarea
+    id: logs4
+    attributes:
+      label: Additional Information
+      description: Include any other relevant information, any images or videos, such as related issues, links to documentation, or any workarounds if they exist.
+  - type: textarea
+    id: logs5
+    attributes:
+      label: Environment (please complete the following information)
+      value: |
+        1. Dokan Version: [e.g. v3.1.2]
+        2. Dokan Pro Version: [e.g. v3.1.2]
+        3. WooCommerce Version: [e.g. v4.9.2]
+        4. Browser [e.g. chrome, safari]
+        5. Current Theme: [e.g. Store Front]
+      render: shell

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,31 @@
+name: Feature Request
+description: File a feature request
+projects: ["dokan-plugin"]
+assignees:
+  - dokan
+body:
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when....
+    validations:
+      required: true
+  - type: textarea
+    id: what-happened1
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: what-happened2
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: what-happened3
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here.
+

.github/pull_request_template.md

@@ -5,6 +5,7 @@
 * [ ] My code is tested
 * [ ] My code passes the PHPCS tests
 * [ ] My code has proper inline documentation
+* [ ] I've included related pull request(s) (optional)
 * [ ] I've included developer documentation (optional)
 * [ ] I've added proper labels to this pull request
 
@@ -16,19 +17,42 @@
 
 <!-- Describe the changes made to this Pull Request and the reason for such changes. -->
 
-Closes # .
+### Related Pull Request(s)
 
-### How to test the changes in this Pull Request:
+* Full PR Link
+
+
+### Closes 
+
+* Closes #
 
-1.
-2.
-3.
 
+### How to test the changes in this Pull Request:
+
+* Steps or issue link
 
 
 ### Changelog entry
 
-> Enter a summary of all changes on this Pull Request. This will appear in the changelog if accepted.
+*Title*
+
+Detailed Description of the pull request. What was previous behaviour
+and what will be changed in this PR.
+
+
+### Before Changes
+
+Describe the issue before changes with screenshots(s).
+
+
+### After Changes
+
+Describe the issue after changes with screenshot(s).
+
+
+### Feature Video (optional)
+
+Link of detailed video if this PR is for a feature.
 
 
 ### PR Self Review Checklist: