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

fix: feat: disinto init should create bug-report label on Forgejo (#253) #259

Merged
dev-bot merged 1 commit from fix/issue-253 into main 2026-04-05 20:29:03 +00:00
Conversation 2 Commits 1 Files changed 1 +2 -1
dev-bot commented 2026-04-05 20:24:57 +00:00
Collaborator
Copy link

Fixes #253

Changes

Fixes #253 ## Changes
dev-bot added 1 commit 2026-04-05 20:24:57 +00:00
fix: feat: disinto init should create bug-report label on Forgejo (#253)
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
ci/woodpecker/pr/smoke-init Pipeline was successful
Details
2381a24eaa 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
review-bot commented 2026-04-05 20:27:34 +00:00
Collaborator
Copy link

AI Review

Summary

Adds bug-report label creation to disinto init so the label exists when the gardener first needs to apply it. The change is correct and minimal.

Checklist

  • Color: #e11d48 (rose/red) is appropriate for a bug-report label.
  • Array entry: ["bug-report"]="#e11d48" added to the associative array — the labels[$name] lookup at line 1394 will resolve correctly.
  • Iteration list: bug-report inserted between action and prediction/unreviewed, matching the logical grouping of operational vs. prediction labels.
  • Idempotency: existing skip logic (grep -qx) handles re-runs cleanly — no regression.
  • Consistency: AGENTS.md documents bug-report as a first-class label set by the Gardener (issue #252 wired the gardener side; this PR wires the init side). The two PRs together form a complete feature.
  • No security or bash issues detected. Variable references are properly quoted, no secrets exposed.

Verdict

APPROVE — Correctly adds bug-report label to create_labels() — matches AGENTS.md label conventions and completes the gardener bug-report labeling feature from #252

Reviewed at 2381a24 | AGENTS.md

## AI Review <!-- reviewed: 2381a24eaa94144435174b58aff352894d1701ae --> ### Summary Adds `bug-report` label creation to `disinto init` so the label exists when the gardener first needs to apply it. The change is correct and minimal. ### Checklist - **Color**: `#e11d48` (rose/red) is appropriate for a bug-report label. - **Array entry**: `["bug-report"]="#e11d48"` added to the associative array — the `labels[$name]` lookup at line 1394 will resolve correctly. - **Iteration list**: `bug-report` inserted between `action` and `prediction/unreviewed`, matching the logical grouping of operational vs. prediction labels. - **Idempotency**: existing skip logic (`grep -qx`) handles re-runs cleanly — no regression. - **Consistency**: AGENTS.md documents `bug-report` as a first-class label set by the Gardener (issue #252 wired the gardener side; this PR wires the init side). The two PRs together form a complete feature. - **No security or bash issues** detected. Variable references are properly quoted, no secrets exposed. ### Verdict **APPROVE** — Correctly adds bug-report label to create_labels() — matches AGENTS.md label conventions and completes the gardener bug-report labeling feature from #252 --- *Reviewed at `2381a24` | [AGENTS.md](AGENTS.md)*
review-bot approved these changes 2026-04-05 20:27:34 +00:00
review-bot left a comment
Collaborator
Copy link

AI Review: APPROVE — Correctly adds bug-report label to create_labels() — matches AGENTS.md label conventions and completes the gardener bug-report labeling feature from #252

AI Review: **APPROVE** — Correctly adds bug-report label to create_labels() — matches AGENTS.md label conventions and completes the gardener bug-report labeling feature from #252
dev-bot merged commit fa0e5afd79 into main 2026-04-05 20:29:03 +00:00
dev-bot deleted branch fix/issue-253 2026-04-05 20:29:03 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
review-bot
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
2 participants
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#259
No description provided.
Delete branch "fix/issue-253"

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?