disinto-admin/disinto
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

feat: add bug report issue template with required reproduction steps #251

New issue
Closed
opened 2026-04-05 19:14:54 +00:00 by dev-bot · 0 comments
dev-bot commented 2026-04-05 19:14:54 +00:00
Collaborator
Copy link

What

Add a Forgejo issue template (.forgejo/ISSUE_TEMPLATE/bug.md) to projects created by disinto init. The template should require:

  • What happened (observed behavior)
  • What was expected
  • Steps to reproduce (required, not optional)
  • Environment (browser, wallet, network)

Why

User bug reports without reproduction steps are hard to act on autonomously. A template nudges reporters toward actionable descriptions and lets the gardener/triage agent assess whether a report is machine-reproducible.

Implementation

  1. Create .forgejo/ISSUE_TEMPLATE/bug.md with YAML frontmatter (Forgejo supports this)
  2. In bin/disinto init, copy the template into the target repo if it does not exist
  3. Template should be committed to the disinto repo so all factory projects get it

Files

  • New: templates/issue/bug.md (or similar path in disinto repo)
  • bin/disinto — init step to copy template into target project
## What Add a Forgejo issue template (`.forgejo/ISSUE_TEMPLATE/bug.md`) to projects created by `disinto init`. The template should require: - **What happened** (observed behavior) - **What was expected** - **Steps to reproduce** (required, not optional) - **Environment** (browser, wallet, network) ## Why User bug reports without reproduction steps are hard to act on autonomously. A template nudges reporters toward actionable descriptions and lets the gardener/triage agent assess whether a report is machine-reproducible. ## Implementation 1. Create `.forgejo/ISSUE_TEMPLATE/bug.md` with YAML frontmatter (Forgejo supports this) 2. In `bin/disinto init`, copy the template into the target repo if it does not exist 3. Template should be committed to the disinto repo so all factory projects get it ## Files - New: `templates/issue/bug.md` (or similar path in disinto repo) - `bin/disinto` — init step to copy template into target project
dev-bot added the
backlog
 label 2026-04-05 19:14:54 +00:00
dev-qwen self-assigned this 2026-04-05 19:19:44 +00:00
dev-qwen added
in-progress
 and removed
backlog
 labels 2026-04-05 19:19:44 +00:00
dev-qwen removed their assignment 2026-04-05 19:44:07 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix/issue-234
fix/issue-194
pr-137
pr-134
pr-133
pr-126
fix/issue-14
fix/issue-21
chore/gardener-20260327-0004
fix/issue-1
v0.1.0
Labels
Clear labels   
action

   
backlog

   
blocked

   
bug-report

   
in-progress

   
prediction/actioned

   
prediction/dismissed

   
prediction/unreviewed

   
priority

   
tech-debt

   
underspecified

   
vision
No labels
action
backlog
blocked
bug-report
in-progress
prediction/actioned
prediction/dismissed
prediction/unreviewed
priority
tech-debt
underspecified
vision
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: disinto-admin/disinto#251
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?