Update templates.

Author: gjwgit

.githooks/README.md

@@ -0,0 +1,19 @@
+The git hooks are located in a non-standard place (other than
+.git/hooks) so that they can be added to github. Seems like files in
+.git can not be added to github.
+
+To enable the hooks in here to be run by git, ensure you first run:
+
+git config core.hooksPath .githooks
+
+To check the current path:
+
+git config core.hooksPath
+
+And to unset the variable:
+
+git config --unset core.hooksPath
+
+The default folder for githooks is .git/hooks.
+
+20250627 gjw

.githooks/pre-commit

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+
+# Dart Format
+
+printf "\e[33;1m%s\e[0m\n" 'Running dart format.'
+
+result=$(dart format lib)
+result_lines=$(echo "$result" | wc -l)
+
+if [ "$result_lines" -gt 1 ]; then
+  echo "$result"
+  printf "\e[31;1m%s\e[0m\n" 'Dart format applied changes, please commit again.'
+  exit 1
+fi
+
+echo "$result"
+printf "\e[32;1m%s\e[0m\n" 'Finished running dart format.'
+
+# Get the commit message.
+
+COMMIT_MSG=$(git log -1 --pretty=%B)
+
+# 20260123 gjw Check if the commit message starts with 'Bump version'
+# If it does then run `make versions` to update the version in any
+# files that require updating, based on the version from pubspec.yaml.
+# Then add any updated files to the commit. I add specific files
+# rather than using `.` just to avoid possibly adding things I was not
+# planning to. This way we always update, for example, the snap
+# version when we 'Bump version', avoiding missing this step, so the
+# installer builds that 'Bump version' triggers will get the correct
+# versions.
+
+if [[ $COMMIT_MSG == Bump\ version* ]]; then
+    printf "\e[33;1m%s\e[0m\n" 'Update versions.'
+
+    make versions
+    git add snap/snapcraft.yaml
+
+    printf "\e[32;1m%s\e[0m\n" 'Finished updating versions.'
+
+fi

.githooks/pre-push

@@ -0,0 +1,38 @@
+#!/usr/bin/env bash
+
+# Verify what is about to be pushed.
+#
+# Called by "git push" after it has checked the remote status, but
+# before anything has been pushed.
+#
+# If this script exits with a non-zero status nothing will be pushed.
+
+# Flutter Analyze
+
+printf "\e[33;1m%s\e[0m\n" 'Running flutter analyze.'
+
+result=$(flutter analyze lib)
+
+if [ $? -ne 0 ]; then
+  echo -e "$result \n"
+  printf "\e[31;1m%s\e[0m\n" 'Flutter analyze found the above issues, please fix, commit and push again.'
+  exit 1
+fi
+
+echo "$result"
+
+# Check the version is updated before we can push!
+
+PVER=$(egrep '^version:' pubspec.yaml | cut -d' ' -f2 | cut -d'+' -f1)
+
+if [ -d snap ]; then
+    SVER=$(egrep '^version:' snap/snapcraft.yaml | cut -d' ' -f2 | cut -d'+' -f1)
+
+    if [ "${PVER}" != "${SVER}" ]; then
+	printf "\e[31;1m%s\e[0m\n" "Version mismatch pubspec.yaml (${PVER}) and snap/snapcraft.yaml (${SVER})."
+	echo 'Run `make versions` and then commit.'
+	exit 2
+    fi
+fi
+
+printf "\e[32;1m%s\e[0m\n" "Finished running Flutter analyze with 0 issues and found Version ${PVER}."

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,6 +1,6 @@
 ---
 name: 'bug report'
-about: Create a bug report to help improve FilePod.
+about: Create a bug report to help improve Rattle.
 title: ''
 labels: ''
 assignees: ''
@@ -13,7 +13,7 @@ assignees: ''
 
 ## To Reproduce
 
-Steps to reproduce the behaviour:
+Steps to reproduce the behavior:
 
 1. Go to '...'
 2. Click on '....'

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,6 +1,6 @@
 ---
 name: 'feature request'
-about: Suggest an idea or feature improvement for FilePod.
+about: Suggest an idea or feature improvement for this project.
 title: ''
 labels: ''
 assignees: ''

.github/pull_request_template.md

@@ -1,27 +1,25 @@
-# Pull Request Details
+## Pull Request Details
 
-## What issue does this PR address
+### Description
+<!--- Describe the problem this PR solves -->
+<!--- Describe what you have changed -->
+<!--- Describe why this change is required -->
 
-- [Description]
+### Related Issues
+<!--- If it fixes an open issue(s), please link to the issue here. -->
 
-## Associated Issue
-
-- This PR relates to issue #
-
-## Type of Change
+### Type of Change
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 - [ ] This change requires a documentation update
 
-## How Has This Been Tested?
-
-Please describe the tests that you ran to verify your changes.
+### How To Test?
+<!--- Describe the tests that a reviewer can undertake to verify your changes. -->
 
-## Checklist
-
-Complete the check-list below to ensure your branch is ready for PR.
+### Checklist
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
 
 - [ ] Screenshots included in linked issue #
 - [ ] Changes adhere to the [style and coding guidelines](https://survivor.togaware.com/gnulinux/flutter-style.html)
@@ -43,9 +41,8 @@ Complete the check-list below to ensure your branch is ready for PR.
 - [ ] I have identified reviewers
 - [ ] The PR has been approved by reviewers
 
-## Finalising
-
-Once PR discussion is complete and reviewers have approved:
+### Finalising
+<!--- Once PR discussion is complete and reviewers have approved. -->
 
 - [ ] Merge dev into the this branch
 - [ ] Resolve any conflicts

.github/workflows/ci.yaml

@@ -1,12 +1,19 @@
 name: Lint Checks
 
+# Always run the checks on a push and a PR.
+#
+# 20250914 gjw Run the tests as separate jobs so we see the individual
+# results. We can instead run then as a single job with multiple
+# steps, but then it stops on the first fail and so not as
+# informative.
+
 on:
   push:
   pull_request:
     types: [opened, reopened, synchronize]
 
 env:
-  FLUTTER_VERSION: '3.38.9'
+  FLUTTER_VERSION: '3.41.5'
 
 jobs:
 
@@ -82,26 +89,41 @@ jobs:
         with:
           node-version: 18
       - run: npm install -g markdownlint-cli
-      - run: markdownlint *.md lib assets
+      - run: markdownlint *.md lib assets installers
 
   link_checker:
     runs-on: ubuntu-latest
     if: github.event.repository.private == false
     permissions:
-      issues: write
+      issues: write # required for peter-evans/create-issue-from-file
     steps:
       - uses: actions/checkout@v4
 
       - name: Link Checker
         id: lychee
         uses: lycheeverse/lychee-action@v2
-        with:
+        with: # Don't fail for now but then create an issue - useful?
           args:
+            --exclude-file .lycheeignore
             --no-progress
             '*.md'
             './**/*.dart'
+            'assets/**/*.md'
+            'assets/**/*.html'
           fail: true
 
+      # 20251030 gjw Remove the automatic creation of an issue for
+      # now. It is creating too many and I am simply closing them. The
+      # failure of the lint test itself should be enough.
+
+      # - name: Create Issue From File
+      #   if: steps.lychee.outputs.exit_code != 0
+      #   uses: peter-evans/create-issue-from-file@v5
+      #   with:
+      #     title: Link Checker Report
+      #     content-filepath: ./lychee/out.md
+      #     labels: report, automated issue
+
   locmax:
     runs-on: ubuntu-latest
     if: github.event.repository.private == false
@@ -116,6 +138,7 @@ jobs:
       - uses: actions/checkout@v4
       - name: Check copyright headers
         run: |
+          # Find Dart files without proper copyright headers, excluding generated files
           missing_copyright=$(find lib -type f -name '*.dart' \
             ! -name '*.g.dart' \
             ! -name '*.gr.dart' \
@@ -125,9 +148,50 @@ jobs:
             ! -name '*.config.dart' \
             -exec grep -L "Copyright" {} \;)
           if [ -n "$missing_copyright" ]; then
-            echo "Files missing copyright headers:"
+            echo "❌ Files missing copyright headers:"
             echo "$missing_copyright"
+            echo ""
+            echo "💡 Note: Generated files (*.g.dart, *.freezed.dart, etc.) are automatically excluded"
+            exit 1
+          else
+            echo "✅ All non-generated Dart files have copyright headers"
+          fi
+
+  # 20251017 gjw The usual command for running the integration tests
+  # is `flutter test interaction_test` and each `*_test.dart`  is
+  # run. However for our testing of apps using solidui we need to
+  # authenticate through an external browser login. The usual `flutter
+  # test` will not properly authenticate. Instead, we should run `make
+  # qtest.all` to run the tests. This action
+
+  test_enforcement:
+    runs-on: ubuntu-latest
+    if: github.event.repository.private == false
+    steps:
+      - uses: actions/checkout@v4
+      - name: Check for batch test commands
+        run: |
+          # Check for disallowed "flutter test integration_test/" usage in scripts/workflows
+          # Exclude comments and this CI check itself
+          batch_test_found=$(grep -r "flutter test integration_test" \
+            .github/workflows/ \
+            support/ \
+            scripts/ \
+            Makefile 2>/dev/null | \
+            grep -v "# Check for disallowed" | \
+            grep -v "batch_test_found=" | \
+            grep -v "echo.*flutter test integration_test/" || true)
+          if [ -n "$batch_test_found" ]; then
+            echo "❌ Found disallowed batch test command 'flutter test integration_test/'"
+            echo ""
+            echo "Found in:"
+            echo "$batch_test_found"
+            echo ""
+            echo "⚠️  Batch testing fails on desktop due to Flutter framework limitations."
+            echo "✅ Use 'make qtest' instead - it runs tests individually."
+            echo ""
+            echo "See docs/TESTING_GUIDE.md for details."
             exit 1
           else
-            echo "All non-generated Dart files have copyright headers"
+            echo "✅ No batch test commands found - using recommended 'make qtest' approach"
           fi