feat: port issue templates to GitHub Issue Forms - #335
Merged
Conversation
This repository's only issue forms lived under `.forgejo/issue_template/`. GitHub is the fleet's only host, so those forms are invisible to everyone filing an issue here. Two approved fleet changes make this urgent: 1. `.forgejo/` is being removed fleet-wide. Without this port that removal would delete the only issue forms this repo has, leaving contributors with a blank issue box. 2. The shared library's `DEFAULT_FORGE` moves from `codeberg` to `github`. The in-product "Request a feature" deep-link then targets a GitHub Issue Form named exactly `feature-request.yml`. If that file is absent GitHub silently drops every pre-filled field instead of erroring, so the app context (app, page, surface, object, spec-ref) would be lost without a single visible failure. Copies all four templates to `.github/ISSUE_TEMPLATE/`, keeping the filenames identical. `.forgejo/` is deliberately left untouched; its removal is a separate later change. Conversion is lossless: Forgejo's issue-template schema is derived from GitHub's, and every construct used here (markdown/input/textarea/dropdown blocks, `render: shell`, `validations.required`, `labels`, `assignees`, `title`) is valid GitHub issue-form syntax. Nothing was dropped or reworded. The top-level `type: "Feature"` in feature-request.yml was verified against the ConductionNL org issue types, where "Feature" exists and is enabled. No `config.yml` was added: `.forgejo/issue_template/` has no equivalent.
rubenvdlinde
requested review from
Rem-Dam,
SudoThijn,
WilcoLouwerse,
bbrands02,
remko48 and
rjzondervan
as code owners
August 24, 2026 17:04
Contributor
Quality Report — ConductionNL/launchpad @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ⏭️ | ||||
| phpcs | ⏭️ | ||||
| phpmd | ⏭️ | ||||
| psalm | ⏭️ | ||||
| phpstan | ⏭️ | ||||
| phpmetrics | ⏭️ | ||||
| eslint | ⏭️ | ||||
| stylelint | ⏭️ | ||||
| build | ⏭️ | ||||
| composer | ⏭️ | ⏭️ | |||
| npm | ⏭️ | ⏭️ | |||
| app:check-code | ⏭️ | ||||
| info.xml | ⏭️ | ||||
| REUSE | ⏭️ | ||||
| PHPUnit | ❌ | ||||
| Newman | ❌ | ||||
| Playwright | ❌ | ||||
| Hydra gates | ❌ |
Quality workflow — 2026-08-24 17:36 UTC
Download the full PDF report from the workflow artifacts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
This repository's only issue forms live under
.forgejo/issue_template/. There is no.github/ISSUE_TEMPLATE/, so on GitHub — the fleet's only host — contributors get a blank issue box today.This is a prerequisite for two approved fleet changes:
.forgejo/is being removed fleet-wide. Without this port, that removal deletes the only issue forms this repo has.DEFAULT_FORGEmoves fromcodebergtogithub. The in-product "Request a feature" deep-link then targets a GitHub Issue Form named exactlyfeature-request.yml. If that file does not exist, GitHub silently drops the pre-filled fields rather than erroring — the app/page/surface/object/spec-ref context would be lost with no visible failure.What changed
Copied all four templates to
.github/ISSUE_TEMPLATE/, filenames unchanged:bug-report.ymlfeature-request.ymltechnical-task.ymluser-story.yml.forgejo/is untouched — no file under it is modified or deleted. Its removal is a separate later change.Dropped in conversion: nothing
Forgejo's issue-template schema is derived from GitHub's, and every construct these files use is valid GitHub issue-form syntax. The ported files are byte-identical to their
.forgejo/originals — this is a location change, not a rewrite. Specifically verified as supported:markdown,input,textarea,dropdown— all with the attributes their type requires.textareawithrender: shell(the Logs field).validations.requiredbooleans,labelsarrays,assignees: [],titleprefixes, emoji innameand in dropdown options.type: "Feature"infeature-request.yml— checked against the ConductionNL org issue types, where an enabled type namedFeatureexists, so this resolves rather than breaking the form.No
config.ymlwas added:.forgejo/issue_template/has no equivalent, and inventing one is out of scope.Validation
yaml.safe_load).name,description,body; every body block has a validtypeplus theattributesthat type requires; everyidis unique within its file; everyvalidations.requiredis a boolean..github/ISSUE_TEMPLATE/feature-request.ymlexists under exactly that name — the deep-link depends on it.git statusshows only additions under.github/ISSUE_TEMPLATE/; nothing under.forgejo/changed.