No description
The Report Issue button (older deployed build) stamps claude-queue at creation, so triage skipped those issues and they went straight to auto-fix (e.g. #37, a large localization feature that should be interactive). Triage now claims a portal issue until it carries a new `triaged` marker (or is in progress/done) — claude-queue is no longer a skip reason. On routing to interactive it strips the stray claude-queue; on claude-queue it adds triaged. Manual queue still works for NON-portal issues (triage never claims those). Resilient regardless of which button build is deployed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .forgejo | ||
| App | ||
| automation | ||
| Docs | ||
| GstService | ||
| Progress | ||
| static | ||
| Wireframe | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| generate_po.py | ||
| inspect_po.py | ||
| test-report-2026-05-17.md | ||