chore: github workflow templates

Author: abose

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,68 @@
+name: 🐞 Bug Report
+title: 'Give a title here'
+description: Report a bug
+labels: ['bug']
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## First of all
+        1. Please search for [existing issues](https://github.com/phcode-dev/phoenix/issues) about this problem first.
+        2. Make sure `rustc` and all relevant Tauri packages are up to date.
+        3. Make sure it's an issue with Tauri and not something else you are using.
+        4. Remember to follow our community guidelines and be friendly.
+        5. Gif screen recordings help more if present. You can use one of the below free screen recorders:
+           1. windows: https://www.screentogif.com/
+           2. mac: https://apps.apple.com/au/app/giphy-capture-the-gif-maker/id668208984?mt=12
+           3. linux:  https://github.com/phw/peek
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the bug
+      description: A clear description of what the bug is. Include screenshots if applicable.
+      placeholder: Bug description
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. Go to ...
+        2. Click on ...
+        3. See error
+
+  - type: textarea
+    id: expected-behavior
+    attributes:
+      label: Expected behavior
+      description: A clear description of what you expected to happen.
+
+  - type: textarea
+    id: info
+    attributes:
+      label: OS, Browser and Phoenix versions
+      description: "goto Help menu > About Phoenix and copy the line that looks like `Release 3.0 development build 3.0.2-0`"
+      placeholder: |
+        1. OS: [e.g. macos]
+        1. device: [mobile, tablet, desktop or other]
+        2. Browser [e.g. chrome, safari]
+        3. Version [e.g. Release 3.0 development build 3.0.2-0]
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs or debug stack trace if any
+    attributes:
+      label: Stack trace
+      render: shell
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,4 @@
+contact_links:
+  - name: 💬 Discord Chat
+    url: https://discord.com/invite/rBpTBPttca
+    about: Ask questions and talk to other Phoenix/Brackets users and the maintainers

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+---
+name: 📚 Docs Report
+about: Create a report to help us improve the docs
+title: "[docs] "
+labels: 'documentation '
+assignees: ''
+
+---

.github/ISSUE_TEMPLATE/docs_report.md

@@ -0,0 +1,35 @@
+name: 💡 Feature Request
+title: '[feat] '
+description: Suggest an idea
+labels: 'Feature Request '
+
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Describe the problem
+      description: A clear description of the problem this feature would solve
+      placeholder: "I'm always frustrated when..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: "Describe the solution you'd like"
+      description: A clear description of what change you would like
+      placeholder: "I would like to..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: "Any alternative solutions you've considered"
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,34 @@
+<!--
+Update "[ ]" to "[x]" to check a box
+-->
+
+### What kind of change does this PR introduce?
+<!-- Check at least one. If you are introducing a new binding, you must reference an issue where this binding has been proposed, discussed and approved by the maintainers. -->
+
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Docs
+- [ ] New Binding issue #___
+- [ ] Code style update
+- [ ] Refactor
+- [ ] Build-related changes
+- [ ] Other, please describe:
+
+### Does this PR introduce a breaking change?
+<!-- If yes, please describe the impact and migration path for existing applications in an attached issue. -->
+
+- [ ] Yes, and the changes were approved in issue #___
+- [ ] No
+
+### Checklist
+- [ ] When resolving issues, they are referenced in the PR's title (e.g `fix: remove a typo, closes #___, #___`)
+- [ ] A change file is added if any packages will require a version bump due to this PR per [the instructions in the readme](https://github.com/tauri-apps/tauri/blob/dev/.changes/readme.md).
+- [ ] I have added a convincing reason for adding this feature, if necessary
+
+### Other information
+
+
+### pull request guidelines:
+* It's OK to have multiple small commits as you work on the PR - we will let GitHub automatically squash it before merging.
+* If adding new feature:, Provide convincing reason to add this feature. Ideally you should open a suggestion issue first and have it greenlighted before working on it.
+* If fixing a bug:Provide detailed description of the bug in the PR, or link to an issue that does.