feat(v0.13.1): hotfix bundle — workflows, donate/dev surfaces, SEO, horror warnings

- workflows: narrow notify-* triggers to specific producer names so non-matching
  workflow_run events don't instantiate a run (kills the Actions tab Skipped spam)
- workflows: auto-link each published release to a GitHub Discussion under
  Announcements via a new link-discussion job before the Discord announce
- repo: add FUNDING.yml + ISSUE_TEMPLATE/{config,bug_report,feature_request}.yml
- docs: add docs/pc_spec.md, docs/dev_env.md (+ VI mirrors) and webapp/TAURI.md
- about: restructure AboutPage with Donate / Dev Environment sections, expanded
  socials (Bluesky, Mastodon, Steam, Telegram bot+user, email, game Discord);
  Ko-fi / Patreon moved from ABOUT.socials to new @config/donate
- header: persistent Donate button (Ko-fi) left of the language switcher
- sidebar: external Report Bug item linking directly to the bug_report template
- seo: full <head> metadata (description, OG, Twitter card, JSON-LD
  WebApplication, 6 locale alternates), per-route useDocumentTitle hook applied
  to all 9 pages, robots.txt, sitemap.xml, manifest.webmanifest, placeholder
  favicon.svg
- warnings: new "horror_specific" group with 7 IDs (eye_horror, body_horror,
  face_horror, cosmic_horror, extreme_gore, decay_rot, mutilation), localized
  to en/vi/ja/es/ko/zh in both ui.json and templates.json

Additive only — no breaking changes to the engine, store schema, or persisted
content-warning IDs. _schema.json updated to reflect new keys.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 4.7 committed 2026-05-11 21:30:39 +07:00
1 parent b4919d6075
commit ebb819eec9
49 files changed
+1162 -90

No files matched your search

+6
View File
@@ -0,0 +1,6 @@
github: poli0981
ko_fi: skullmute
buy_me_a_coffee: skullmute
patreon: skullmute
custom:
- paypal.me/DungDang212
+99
View File
@@ -0,0 +1,99 @@
name: Bug report
description: Something is broken or behaving unexpectedly.
title: "[Bug]: "
labels: ["bug", "triage"]
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to file a bug. Please fill in as much detail as you can —
a clear reproduction is the difference between a fix today and a fix in 3 weeks.
- type: input
id: version
attributes:
label: App version
description: From the About page or the title bar. Example `v0.13.0`.
placeholder: v0.13.0
validations:
required: true
- type: dropdown
id: surface
attributes:
label: Where are you running YTDescGen?
options:
- Web (GitHub Pages)
- Desktop — Windows (Tauri)
- Desktop — macOS (Tauri)
- Desktop — Linux (Tauri)
- Local dev (npm run dev)
validations:
required: true
- type: input
id: os
attributes:
label: Operating system
description: e.g. Windows 11 25H2, macOS 14.6, Ubuntu 24.04
validations:
required: true
- type: input
id: browser
attributes:
label: Browser (web only)
description: e.g. Chrome 131, Brave 1.70, Safari 17. Leave blank for desktop.
- type: dropdown
id: language
attributes:
label: App language at the time of the bug
options:
- English (en)
- Tiếng Việt (vi)
- 日本語 (ja)
- Español (es)
- 한국어 (ko)
- 中文 (zh)
validations:
required: true
- type: textarea
id: repro
attributes:
label: Steps to reproduce
description: Numbered steps. Include the exact inputs that triggered the bug.
placeholder: |
1. Open Editor
2. Pick genre "Survival Horror"
3. Toggle "eye_horror" warning
4. Click Generate
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected behavior
validations:
required: true
- type: textarea
id: actual
attributes:
label: Actual behavior
validations:
required: true
- type: textarea
id: console
attributes:
label: Console / log output
description: Open DevTools (web) or the log panel (desktop) and paste any errors. Rendered as code.
render: shell
- type: textarea
id: screenshots
attributes:
label: Screenshots / screen recording (optional)
description: Drag and drop images or videos here.
- type: checkboxes
id: checks
attributes:
label: Pre-flight checks
options:
- label: I searched existing issues and this is not a duplicate.
required: true
- label: I'm on the latest released version (or noted my older version above).
required: true
+8
View File
@@ -0,0 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: Discord — General chat
url: https://discord.gg/2aNR3aVt
about: For casual questions, gameplay chat, or quick help. Use a bug report or feature request for anything actionable.
- name: GitHub Discussions
url: https://github.com/poli0981/youtube-generator/discussions
about: Ideas, Q&A, and release announcements live here.
@@ -0,0 +1,48 @@
name: Feature request
description: Suggest a new feature or improvement.
title: "[Feature]: "
labels: ["enhancement", "triage"]
body:
- type: textarea
id: problem
attributes:
label: Problem
description: What pain point or workflow gap are you running into today?
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed solution
description: What should YTDescGen do? Be concrete — UI sketch, example output, etc.
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Other approaches you thought about and why you ruled them out.
- type: dropdown
id: scope
attributes:
label: Scope
description: Which surfaces does this affect?
multiple: true
options:
- Editor
- Output / preview
- Profiles / presets
- Templates (description, title, tags)
- i18n / locales
- Settings
- Desktop (Tauri)
- Documentation
validations:
required: true
- type: checkboxes
id: checks
attributes:
label: Pre-flight checks
options:
- label: I searched existing issues and this is not a duplicate.
required: true
+21 -3
View File
@@ -10,13 +10,31 @@ on:
required: true
type: string
# Reusable announce-release.yml only needs `contents: read` to fetch
# release metadata via the gh CLI.
# `link-discussion` needs `contents: write` (to edit the release) and
# `discussions: write` (so GitHub auto-creates the linked Discussion under
# the configured category). The reusable announce job only needs read.
permissions:
contents: read
contents: write
discussions: write
jobs:
link-discussion:
runs-on: ubuntu-latest
steps:
- name: Link release to Announcements discussion
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Setting --discussion-category on a published release causes
# GitHub to auto-create the linked Discussion. Requires the
# repo to have Discussions enabled with an "Announcements"
# category (configured manually under repo Settings).
run: |
gh release edit "${{ github.event.release.tag_name || inputs.tag }}" \
--repo "${{ github.repository }}" \
--discussion-category "Announcements"
announce:
needs: link-discussion
uses: poli0981/.github/.github/workflows/announce-release.yml@main
with:
tag_override: ${{ inputs.tag || '' }}
+3 -1
View File
@@ -2,7 +2,9 @@ name: Notify CI Failures
on:
workflow_run:
workflows: ["*"]
# Match the exact `name:` of the CI workflow (.github/workflows/ci.yml).
# Renaming CI silently breaks this filter — keep them in sync.
workflows: ["CI"]
types: [completed]
# REQUIRED: declare permissions matching the reusable workflow's needs.
+4 -1
View File
@@ -2,7 +2,10 @@ name: Notify Deploy Status
on:
workflow_run:
workflows: ["*"]
# Match the exact `name:` of the deploy workflow
# (.github/workflows/deploy-web.yml). Renaming it silently breaks this
# filter — keep them in sync.
workflows: ["Deploy to GitHub Pages"]
types: [completed]
permissions:
@@ -2,7 +2,10 @@ name: Notify Release Pipeline
on:
workflow_run:
workflows: ["*"]
# Match the exact `name:` of the release-pipeline producers
# (release-desktop.yml + announce-release.yml). Renaming either silently
# breaks this filter — keep them in sync.
workflows: ["Release Desktop", "Announce Release to Discord"]
types: [completed]
permissions: