Theme fest ins Repo uebernehmen statt als Submodule

Ein normaler git clone holt Submodules nicht mit - geprueft: nach dem
Klonen des Repos war themes/gokarna leer. Portainer klont ebenso, der
Build im Container waere also an dem fehlenden Theme gescheitert.

Gokarna liegt jetzt direkt im Repo, festgeschrieben auf Commit 8306042,
den Stand, mit dem die Seite bisher gebaut wurde. .gitmodules entfaellt.

Nachteil: Theme-Updates muessen kuenftig von Hand eingespielt werden.
Dafuer baut das Repo aus jedem beliebigen Klon heraus, ohne
Sonderbehandlung.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

themes/gokarna/.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: gokarna-theme
+buy_me_a_coffee: avijitgupta

themes/gokarna/.github/workflows/screenshot.yml

@@ -0,0 +1,38 @@
+name: Update screenshots
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+
+jobs:
+  update-screenshots:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+      contents: write
+
+    steps:
+    - name: Check out the code
+      uses: actions/checkout@v3
+
+    - name: Run screenshotter container
+      run: docker run -v $(pwd):/app ghcr.io/gokarna-theme/gokarna-hugo/screenshotter
+
+    - name: Create PR
+      run: |
+        if [[ -z $(git status images --porcelain) ]]; then
+          echo "No changes found"
+          exit 0
+        fi
+
+        git config --global user.name 'github-actions[bot]'
+        git config --global user.email 'github-actions[bot]@users.noreply.github.com'
+        git checkout -b auto-update-screenshots
+        git add images/
+        git commit -m 'chore: update screenshots'
+        git push origin auto-update-screenshots -f
+        gh pr create -B main -H auto-update-screenshots --title 'chore: update screenshots' --body 'Created by GitHub action'
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

themes/gokarna/.github/workflows/stale-bot.yml

@@ -0,0 +1,22 @@
+name: 'Close stale issues and mark inactive PRs'
+on:
+  schedule:
+    - cron: '0 0 * * 0'  # At 00:00 on every Sunday
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      pull-requests: write
+      contents: read
+    steps:
+      - uses: actions/stale@v9
+        with:
+          stale-issue-message: 'This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.'
+          stale-pr-message: 'This PR is stale because it has been open for 90 days with no activity.'
+          close-issue-message: 'This issue was closed due to inactivity'
+          days-before-stale: 90
+          days-before-close: 30
+          days-before-pr-close: -1
+          exempt-all-assignees: true