fix(ci): set loop/code label on Firebase test failure issues #551

Merged
guettlibot merged 1 commits from refs/pull/551/head into main 2026-06-09 14:08:40 +00:00
guettlibot commented 2026-06-09 10:29:21 +00:00 (Migrated from codeberg.org)

Closes #550

Summary

When Firebase instrumented tests fail in the nightly run, the workflow opens a tracking issue. It currently tags it with the legacy Ready label, which is not part of the current agent loop. Switch the label to loop/code so the coding agent picks it up automatically and the error gets fixed.

Change

  • .forgejo/workflows/firebase-tests.yml: set loop/code instead of Ready on the created failure issue.

Test plan

  • Wait for next scheduled (or manually dispatched) Firebase test failure and confirm the created issue carries the loop/code label.
Closes #550 ## Summary When Firebase instrumented tests fail in the nightly run, the workflow opens a tracking issue. It currently tags it with the legacy `Ready` label, which is not part of the current agent loop. Switch the label to `loop/code` so the coding agent picks it up automatically and the error gets fixed. ## Change - `.forgejo/workflows/firebase-tests.yml`: set `loop/code` instead of `Ready` on the created failure issue. ## Test plan - [ ] Wait for next scheduled (or manually dispatched) Firebase test failure and confirm the created issue carries the `loop/code` label.
Sign in to join this conversation.