Merge branch 'Helium314:main' into spellcheck-scripts-url

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+
+liberapay: Helium314

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,7 +4,13 @@ about: Create a report to help us improve
 labels: bug
 ---
 
-<!-- Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the readme.
+<!--
+tl;dr
+* search for duplicates also in closed issues
+* one issue per topic
+* reduce screenshot size
+
+Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the readme.
 If you want to report more issues / bugs, open multiple issues (one for each).
 If you're interested, you can read the following useful text about effective bug reporting (a bit longer read): https://www.chiark.greenend.org.uk/~sgtatham/bugs.html -->
 
@@ -29,9 +35,9 @@ If you add screenshots, reduce the size or use thumbnails to keep the issue nice
 **App version**
 <!-- Which version of this app is affected? If you build the app yourself, please specify the latest commit included in the build -->
 
-**Device (please complete the following information):**
- - Model: <!-- [e.g. Samsung Galaxy S9] -->
- - OS: <!-- [e.g. Android 10] (add details if you are not using a version provided by the device manufacturer) -->
+**Device:**
+ - Model: [e.g. Samsung Galaxy S9]
+ - OS: [e.g. Android 10] (please also mention whether you are using the manufacturer's OS or a custom ROM)
 
 **Additional context**
 <!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -5,6 +5,11 @@ labels: enhancement
 ---
 
 <!--
+tl;dr
+* search for duplicates also in closed issues
+* one issue per topic
+* reduce screenshot size
+
 Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the readme.
 If you have more than one feature request, open multiple issues (one for each) unless the requests are closely related.
 Note that given the number of feature requests and available developer time, it may take a long time until the feature request gets attention.

.github/ISSUE_TEMPLATE/other.md

@@ -4,6 +4,11 @@ about: Anything that does not fit into the other categories. Please don't use th
 ---
 
 <!--
+tl;dr
+* search for duplicates also in closed issues
+* one issue per topic
+* reduce screenshot size
+
 Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the readme.
 Open one issue per topic / request, and do not use this category for bug reports or feature requests.
 

.github/ISSUE_TEMPLATE/spell_checker.md

@@ -0,0 +1,19 @@
+---
+name: Spell checker issue
+about: Issue related to spell checker (this is the component that underlines mis-spelled words in red)
+labels: "spell checker"
+---
+
+<!--
+tl;dr
+* search for duplicates also in closed issues
+* one issue per topic
+* reduce screenshot size
+
+Make sure you actually enabled HeliBoard spell checker. Usually it can be found in System Settings -> System -> Languages -> Advanced -> Spell Checker, but this may depend on Android version.
+Note that the menu when tapping a word underlined in red is coming form the Android system and is not under control of HeliBoard.
+
+Please search open and closed issues to avoid duplicates. Maybe what you want has already been discussed or is mentioned in the readme.
+Open one issue per topic / request, and do not use this category for bug reports or feature requests.
+If you add screenshots, reduce the size or use thumbnails to keep the issue nicely readable.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,12 @@
 <!--
-* Please describe briefly what your pull request proposes to fix or improve.
+See the contributing section in the readme for more detailed guideline: https://github.com/Helium314/HeliBoard?tab=readme-ov-file#guidelines
+Most importantly:
+* The PR should focus on a single contribution.
+* Describe briefly what your pull request proposes to fix or improve.
 * If it's not completely obvious, describe what the PR does to achieve the desired result.
+
+Further
 * If you use someone else's code, please mention or better link to the source.
-* See the contributing section in the readme for more detailed guideline: https://github.com/Helium314/HeliBoard?tab=readme-ov-file#guidelines
+* When the PR contains "fixes" <issue number>, the related issue will be linked and automatically closed if the PR is merged (also works for other words like "fix", "resolve", "resolves", "closes", ...)
+* If you add a layout, make sure you have read https://github.com/Helium314/HeliBoard/blob/main/layouts.md#adding-new-layouts--languages
 -->