Contributing: Aligned templates, labels and workflows with the other repositories

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,64 @@
+name: Bug report
+description: A page looks or behaves differently from GitHub, or breaks, with the theme installed.
+labels:
+  - bug
+body:
+  - type: input
+    id: version
+    attributes:
+      label: Theme version
+      description:
+        For example `0.5.0`, or `dev` for a build from source. A built stylesheet names it in `--theme-version`.
+    validations:
+      required: true
+
+  - type: input
+    id: forgejo-version
+    attributes:
+      label: Forgejo version
+      placeholder: "17.0.0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: installation
+    attributes:
+      label: Installation
+      options:
+        - Stylesheets and template overrides
+        - Stylesheets only
+    validations:
+      required: true
+
+  - type: input
+    id: page
+    attributes:
+      label: Page
+      description: The page and its address, for example the issue list at `/owner/repo/issues`.
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. Open the issue list
+        2. Narrow the window to phone width
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected and actual behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: media
+    attributes:
+      label: Screenshots
+      description: >-
+        The page with the theme and, if you can, the same page on GitHub and in Forgejo's default theme. Hide names or
+        tokens you do not want to share.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,45 @@
+name: Suggestion
+description: Suggest a page or behavior the theme should match, or a change to the existing look.
+labels:
+  - feature
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What looks or works differently from GitHub today, and where.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: How the theme could solve it. A link to or screenshot of the GitHub page helps.
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives
+      description: Workarounds or other solutions you considered.
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - Actions
+        - Code
+        - Dashboard
+        - Issues
+        - Navigation
+        - Organizations
+        - Profile
+        - Projects
+        - Pull requests
+        - Releases
+        - Settings
+        - Themes
+        - Other

.github/dependabot.yml

@@ -0,0 +1,22 @@
+version: 2
+updates:
+  # bun.lock is not committed, so Dependabot updates package.json through the npm ecosystem.
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "Dependency"
+    open-pull-requests-limit: 10
+    labels:
+      - "dependencies"
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      prefix: "Dependency"
+    open-pull-requests-limit: 5
+    labels:
+      - "dependencies"

.github/pull_request_template.md

@@ -0,0 +1,23 @@
+## Summary
+
+<!-- What changes for Forgejo users or admins, and why. -->
+
+## Before and after
+
+<!-- Screenshots of the same page, viewport and state; see "Pull Requests and Release Notes" in CONTRIBUTING.md. -->
+
+## Release notes
+
+<!-- The title and the label decide what the release draft shows. See "Pull Requests and Release Notes" in CONTRIBUTING.md. -->
+
+- [ ] The title follows `Area: Description` with a listed area
+- [ ] The title describes the effect in the past tense, for example `Branches: Fixed ...`
+- [ ] Exactly one label: `feature`, `change`, `bug`, `dependencies`, or `skip-changelog`
+- [ ] `bug` only for a bug that shipped in a release; a fix for a bug that only existed on `dev` is `skip-changelog`
+- [ ] `major` added when admins must act on upgrade, for example a new minimum Forgejo version
+- [ ] Upgrade steps or warnings added to `.github/release-notes.md`, if admins need them
+
+## Checks
+
+- [ ] Tests added or updated
+- [ ] Checked in the dev preview at desktop and phone width, in dark and light mode