Fix issues

.gitea/issue_template/bugreport.yml

@@ -8,10 +8,11 @@ body:
    id: 'text-introduction'
    attributes:
     value: |
-      Hey there! Thank you for taking the time to report a bug report to us.
+      Hey there! Thank you for taking the time to report a bug report to us. \
-      This means a lot to us as that's the only way to get better... and many people don't file bug reports.
+      This means a lot to us as that's the only way to get better... and many people don't file bug reports. \
-      Anyway, please answer the following questions accurately, otherwise we won't be able to help you.
+      Anyway, please answer the following questions accurately, otherwise we won't be able to help you. \
-      **Note: Please check if the same bug report already exists. If not, continue. If so, participate in that one instead.**
+       \
+      **Note: Please check if the same bug report already exists. If not, continue. If so, participate in that one instead.** \
       **Note: Please don't censor anything *except* sensitive information. You don't need to be embarrased about your username. You censor your bug report, we censor our answers.**
  - type: 'textarea'
    id: 'bug-description'
@@ -25,7 +26,7 @@ body:
    id: 'bug-log'
    attributes:
     label: 'Bug log'
-    description: 'For us to understand the problem you're having please insert the ENTIRE log file here. You must give us `DIAG` level logs (set `logger_level` in CORE's configuration to `CoreTypes.LoggerLevel.DIAG` during initialization). **Leave this empty if you give us a reproduction project.**'
+    description: 'For us to understand the problem you''re having please insert the ENTIRE log file here. You must give us `DIAG` level logs (set `logger_level` in CORE''s configuration to `CoreTypes.LoggerLevel.DIAG` during initialization). **Leave this empty if you give us a reproduction project.**'
     placeholder: 'Your log file here...'
     value: |
       <details>
@@ -41,8 +42,10 @@ body:
     description: 'Insert a snippet of your code that you think is causing the issue. **Leave this empty if you give us a reproduction project.**'
     value: |
       <details>
+      ```gdscript
       Your code snippet here...
       Note: We wrap the snippet in the `details` tag so the code doesn't take up too much space in the issue. Please don't remove them.
+      ```
       </details>
    validations:
     required: false
@@ -88,7 +91,7 @@ body:
    id: 'godot-version'
    attributes:
     label: 'Godot Version'
-    description: 'Name the engine version you are using. You can copy it by starting the editor's project manager and clicking on the version text in the top right corner.'
+    description: 'Name the engine version you are using. You can copy it by starting the editor''s project manager and clicking on the version text in the top right corner.'
     placeholder: 'ex. v4.2.1.stable.flathub [b09f793f5]'
    validations:
     required: true
@@ -96,7 +99,7 @@ body:
    id: 'godot-custom'
    attributes:
     label: 'Modified engine vendor'
-    description: 'Name the custom engine name and/or link if the engine you are using isn't directly built from Godot's source code (i.e. a fork). **Leave empty if you're not using a fork of the Godot Engine.**'
+    description: 'Name the custom engine name and/or link if the engine you are using isn''t directly built from Godot''s source code (i.e. a fork). **Leave empty if you''re not using a fork of the Godot Engine.**'
     placeholder: 'e.g. godot-vita (https://github.com/SonicMastr/godot-vita)'
    validations:
     required: false
@@ -104,12 +107,11 @@ body:
    id: 'os'
    attributes:
     label: 'Target operating system'
-    description: 'Name the target operating system, it's version (if applicable) and architecture (if the OS supports more than one architecture) here. If you're developing a phone game and the issue only occurs on Android/iOS, don't name your desktop operating system here.'
+    description: 'Name the target operating system, it''s version (if applicable) and architecture (if the OS supports more than one architecture) here. If you''re developing a phone game and the issue only occurs on Android/iOS, don''t name your desktop operating system here.'
     placeholder: 'e.g. Android 14 on arm64 or Windows 11 on amd64 or Arch Linux or Debian trixie on arm64 or FreeBSD on amd64 or UwUntu or TempleOS'
    validations:
     required: true
  - type: 'markdown'
    id: 'text-tysm'
    attributes:
-    value: |
+    value: 'Thank you for filling out this bug report. Please check your answers before sending this report.'
-     Thank you for filling out this bug report. Please check your answers before sending this report.

.gitea/issue_template/featurerequest.yml

@@ -8,17 +8,18 @@ body:
    id: 'text-introduction'
    attributes:
     value: |
-      Hey there! Thank you for taking the time to report a feature request to us.
+      Hey there! Thank you for taking the time to report a feature request to us. \
-      Before filling any of this out, please think for one minute if the feature is really important and necessary for all/many projects to have.
+      Before filling any of this out, please think for one minute if the feature is really important and necessary for all/many projects to have. \
-      If not it would probably best to write a custom module for the feature you want added.
+      If not it would probably best to write a custom module for the feature you want added. \
-      Please answer the following questions accurately, otherwise we may not be able to add the feature.
+      Please answer the following questions accurately, otherwise we may not be able to add the feature. \
-      **Note: Please check if the same feature request already exists. If not, continue. If so, participate in that one instead.**
+       \
-      **Note: Please don't censor anything *except* sensitive information. You don't need to be embarrased about your username. You censor your bug report, we censor our answers.**
+      **Note: Please check if the same feature request already exists. If not, continue. If so, participate in that one instead.** \
+      **Note: Please don't censor anything *except* sensitive information. You don''t need to be embarrased about your username. You censor your bug report, we censor our answers.**
  - type: 'textarea'
    id: 'feature-description'
    attributes:
     label: 'Feature description'
-    description: 'Explain *what* you want added. Also describe why this feature can't implemented without integrating it into the CORE Framework. Include as many details as possible.'
+    description: 'Explain *what* you want added. Also describe why this feature can''t implemented without integrating it into the CORE Framework. Include as many details as possible.'
     placeholder: |
       Example:
       I want to do XY in my project, which is fairely hard to implement but would benefit a lot of projects.
@@ -32,23 +33,22 @@ body:
     placeholder: |
       Example:
       I would propose to <some description on how to implement your feature>.
-      I've also thought on simply <some other description on how to implement your feature>.
+      I''ve also thought on simply <some other description on how to implement your feature>.
    validations:
     required: true
-- type: 'textarea'
+ - type: 'textarea'
    id: 'feature-alternatives'
    attributes:
     label: 'Feature alternatives'
-    description: 'Explain how could be possible to implement the feature without building it into the framework directly. Include as many details as possible. **Leave empty if it can't simply be solved by adding a module.**'
+    description: 'Explain how could be possible to implement the feature without building it into the framework directly. Include as many details as possible. **Leave empty if it can''t simply be solved by adding a module.**'
     placeholder: |
       Example:
-      I've considered using a custom module for this feature.
+      I''ve considered using a custom module for this feature.
       Otherwise it would be possible to use <link to some project>.
-      I've also considered using the engine's way of doing it by <how to do it using the engine's way>.
+      I''ve also considered using the engine''s way of doing it by <how to do it using the engine''s way>.
    validations:
     required: false
  - type: 'markdown'
    id: 'text-tysm'
    attributes:
-    value: |
+    value: 'Thank you for filling out this feature request form. Please check your answers before sending this report.'
-     Thank you for filling out this feature request form. Please check your answers before sending this report.

.gitea/issue_template/helprequest.yml

@@ -8,9 +8,10 @@ body:
    id: 'text-introduction'
    attributes:
     value: |
-      Hey there! Seems like you have some kind of issue with the CORE Framework.
+      Hey there! Seems like you have some kind of issue with the CORE Framework. \
-      Please answer the following questions accurately, otherwise we won't be able to help you.
+      Please answer the following questions accurately, otherwise we won't be able to help you. \
-      **Note: Please check if someone has had the same issue before. If not, continue. If so, participate in that one instead.**
+       \
+      **Note: Please check if someone has had the same issue before. If not, continue. If so, participate in that one instead.** \
       **Note: Please don't censor anything *except* sensitive information. You don't need to be embarrased about your username. You censor your stuff, we censor our answers.**
  - type: 'textarea'
    id: 'help-description'
@@ -24,7 +25,7 @@ body:
    id: 'help-log'
    attributes:
     label: 'Log'
-    description: 'For us to understand the problem you're having please insert the ENTIRE log file here. You must give us `DIAG` level logs (set `logger_level` in CORE's configuration to `CoreTypes.LoggerLevel.DIAG` during initialization). **Leave this empty if your problem does not need log output or doesn't involve code at all.**'
+    description: 'For us to understand the problem you''re having please insert the ENTIRE log file here. You must give us `DIAG` level logs (set `logger_level` in CORE''s configuration to `CoreTypes.LoggerLevel.DIAG` during initialization). **Leave this empty if your problem does not need log output or doesn''t involve code at all.**'
     placeholder: 'Your log file here...'
     value: |
       <details>
@@ -37,7 +38,7 @@ body:
    id: 'help-snippet'
    attributes:
     label: 'Code snippet'
-    description: 'Insert a snippet of your code that you need help with. **Leave this empty if your problem does not need log output or doesn't involve code at all.**'
+    description: 'Insert a snippet of your code that you need help with. **Leave this empty if your problem does not need log output or doesn''t involve code at all.**'
     value: |
       <details>
       Your code snippet here...
@@ -67,7 +68,7 @@ body:
    id: 'godot-version'
    attributes:
     label: 'Godot Version'
-    description: 'Name the engine version you are using. You can copy it by starting the editor's project manager and clicking on the version text in the top right corner.'
+    description: 'Name the engine version you are using. You can copy it by starting the editor''s project manager and clicking on the version text in the top right corner.'
     placeholder: 'ex. v4.2.1.stable.flathub [b09f793f5]'
    validations:
     required: true
@@ -75,12 +76,11 @@ body:
    id: 'godot-custom'
    attributes:
     label: 'Modified engine vendor'
-    description: 'Name the custom engine name and/or link if the engine you are using isn't directly built from Godot's source code (i.e. a fork). **Leave empty if you're not using a fork of the Godot Engine.**'
+    description: 'Name the custom engine name and/or link if the engine you are using isn''t directly built from Godot''s source code (i.e. a fork). **Leave empty if you''re not using a fork of the Godot Engine.**'
     placeholder: 'e.g. godot-vita (https://github.com/SonicMastr/godot-vita)'
    validations:
     required: false
  - type: 'markdown'
    id: 'text-tysm'
    attributes:
-    value: |
+    value: 'Thank you for filling out this help form. Please check your answers before sending your help request.'
-     Thank you for filling out this help form. Please check your answers before sending your help request.

.gitea/pull_request_template.md

@@ -0,0 +1,12 @@
+---
+name: 'Pull Request'
+about: 'Submit a pull request.'
+title: 'new: '
+ref: 'develop'
+labels:
+ - 'PRStatus/Open'
+ - 'PR/New'
+---
+<!--
+  Please list your changes (if your pull request includes a lot of changes) and name a issue number (if applicable).
+-->

.gitea/pull_request_template/bugfix.md

@@ -1,13 +0,0 @@
----
-name: '🪱 Bugfix'
-about: 'Submit a pull request which fixes a bug in the framework code.'
-title: 'bugfix: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/Bugfix'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/documentation.md

@@ -1,13 +0,0 @@
----
-name: '📚 Documentation'
-about: 'Submit a pull request which updates the documentation. Do not create your pull request with this template if your PR is implementing a new feature or updating dependencies.'
-title: 'docs: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/Documentation'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/miscellaneous.md

@@ -1,13 +0,0 @@
----
-name: '🎯 Miscellaneous'
-about: 'Submit a pull request which does not update the documentation, adds a new feature, introduces quality of life changes, or fixes a bug.'
-title: 'misc: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/Miscellaneous'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/mixed.md

@@ -1,13 +0,0 @@
----
-name: '🧋 Mixed'
-about: 'Submit a pull request which updates multiple regions of the CORE source code and documentation.'
-title: 'mixed: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/Mixed'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/newfeature.md

@@ -1,13 +0,0 @@
----
-name: '➕ New Feature'
-about: 'Submit a pull request which introduces a new feature into the framework.'
-title: 'feat: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/NewFeature'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/qualityoflife.md

@@ -1,13 +0,0 @@
----
-name: '💖 Quality of Life'
-about: 'Submit a pull request which improves the developer experience.'
-title: 'qol: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/QualityOfLife'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->

.gitea/pull_request_template/update.md

@@ -1,13 +0,0 @@
----
-name: '📩 Update'
-about: 'Submit a pull request which updates one of CORE's dependencies.'
-title: 'update: '
-ref: 'develop'
-labels:
- - 'PRStatus/Open'
- - 'PR/Update'
----
-<!--
-  Please name some context on what you've fixed. Also name the issue number (if there is one)
-  and make a list of changes you've made if your pull request includes many changes.
--->