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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
Readylabel, which is not part of the current agent loop. Switch the label toloop/codeso the coding agent picks it up automatically and the error gets fixed.Change
.forgejo/workflows/firebase-tests.yml: setloop/codeinstead ofReadyon the created failure issue.Test plan
loop/codelabel.