Bootstrap: README + issue templates #1

Merged

mik-tf merged 3 commits from development_mik_bootstrap into main

2026-05-20 22:00:31 +00:00

mik-tf commented

2026-05-20 21:44:33 +00:00

Contributor

Two-commit PR setting up the feedback repo so hero_cockpits feedback iframe has a polished surface to land users on.

Commit 1 — issue templates:

.gitea/ISSUE_TEMPLATE/bug.md — title [bug] , labels bug, needs-triage
.gitea/ISSUE_TEMPLATE/feature.md — title [feature] , labels feature-request, needs-triage
.gitea/ISSUE_TEMPLATE/feedback.md — title [feedback] , labels feedback, needs-triage

Commit 2 — README:

Purpose, filing flow with template-aware new-issue URLs, team-side triage flow + label scheme, privacy reminder, cross-links

Context

Meeting minutes: hero_os_tfgrid_deployer#1
Cockpit spec (consumer of this repo): hero_cockpit#1

No Rhai scripts per the meeting decision — cockpit calls Forge REST directly to embed the issue creation flow.

Two-commit PR setting up the feedback repo so hero_cockpits feedback iframe has a polished surface to land users on. Commit 1 — issue templates: - `.gitea/ISSUE_TEMPLATE/bug.md` — title `[bug] `, labels `bug, needs-triage` - `.gitea/ISSUE_TEMPLATE/feature.md` — title `[feature] `, labels `feature-request, needs-triage` - `.gitea/ISSUE_TEMPLATE/feedback.md` — title `[feedback] `, labels `feedback, needs-triage` Commit 2 — README: - Purpose, filing flow with template-aware new-issue URLs, team-side triage flow + label scheme, privacy reminder, cross-links ## Context - Meeting minutes: [hero_os_tfgrid_deployer#1](https://forge.ourworld.tf/lhumina_code/hero_os_tfgrid_deployer/issues/1) - Cockpit spec (consumer of this repo): [hero_cockpit#1](https://forge.ourworld.tf/lhumina_code/hero_cockpit/issues/1) No Rhai scripts per the meeting decision — cockpit calls Forge REST directly to embed the issue creation flow.

mik-tf added 2 commits

2026-05-20 21:44:34 +00:00

feat: bootstrap repo with README + issue templates 7e7ef943c5

The feedback repo is the public channel hero_cockpit's feedback iframe
posts to. Added:

- README describing the purpose, who it's for, what NOT to file here,
  and where the team triage flow lives
- .gitea/ISSUE_TEMPLATE/{bug,feature,feedback}.md — three templates
  matching the three buttons in the cockpit feedback page

References:
- hero_os_tfgrid_deployer#1 (meeting minutes)
- hero_cockpit#1 §3.4 (cockpit feedback flow)

docs: expand README — purpose, filing flow, team triage, privacy f9c81b36b0

Replaces the empty stub README with: what the repo is for, links to
each issue template, what it's NOT (not a support channel, not a code
bugtracker for lhumina_code/), team-side triage flow + label scheme,
privacy reminder, cross-links to the umbrella meeting issue + cockpit
spec.

mik-tf added 1 commit

2026-05-20 21:46:22 +00:00

chore: rename .gitea/ISSUE_TEMPLATE → .forgejo/issue_template a520154796

Match the Forgejo-native convention (forge.ourworld.tf runs Forgejo,
not Gitea). Per Forgejo docs both paths work via backwards-compat
but .forgejo/issue_template/ (lowercase, snake_case) is the preferred
location and what hero_demo already uses for .forgejo/workflows/.