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

feat: gardener should label issues as bug-report when they describe user-facing bugs with repro steps #252

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

The gardener agent should detect issues that describe user-facing broken behavior with reproduction steps and label them bug-report.

Why

This enables downstream automation: a bug-report labeled issue can trigger a reproduction agent, while issues without repro steps stay as underspecified or get groomed further.

Implementation

  1. Add bug-report label detection logic to the gardener formula (formulas/run-gardener.toml)
  2. Criteria: issue body contains steps to reproduce, describes broken behavior (not a feature request), and is not already labeled
  3. The gardener should NOT convert the issue to backlog — bug-report is a separate triage track

Files

  • formulas/run-gardener.toml — add bug-report labeling rule
  • gardener/gardener-run.sh — if label logic is in the shell wrapper
## What The gardener agent should detect issues that describe user-facing broken behavior with reproduction steps and label them `bug-report`. ## Why This enables downstream automation: a `bug-report` labeled issue can trigger a reproduction agent, while issues without repro steps stay as `underspecified` or get groomed further. ## Implementation 1. Add `bug-report` label detection logic to the gardener formula (`formulas/run-gardener.toml`) 2. Criteria: issue body contains steps to reproduce, describes broken behavior (not a feature request), and is not already labeled 3. The gardener should NOT convert the issue to `backlog` — `bug-report` is a separate triage track ## Files - `formulas/run-gardener.toml` — add bug-report labeling rule - `gardener/gardener-run.sh` — if label logic is in the shell wrapper
dev-bot added the
backlog
 label 2026-04-05 19:14:54 +00:00
dev-bot self-assigned this 2026-04-05 20:09:02 +00:00
dev-bot added
in-progress
 and removed
backlog
 labels 2026-04-05 20:09:02 +00:00
dev-bot removed their assignment 2026-04-05 20:14:03 +00:00
dev-bot removed the
in-progress
 label 2026-04-05 20:14:03 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
chore/gardener-20260407-1805
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#252
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?