Build: Fixed bug in permissions, sped up product-verifier slightly
CI / push-validation (push) Successful in 17s
CI / helm (push) Successful in 23s
CI / lint (push) Successful in 26s
CI / quality (push) Successful in 48s
CI / typecheck (push) Successful in 59s
CI / build (push) Successful in 3m18s
CI / e2e_tests (push) Failing after 3m19s
CI / security (push) Successful in 4m27s
CI / integration_tests (push) Successful in 9m55s
CI / unit_tests (push) Successful in 10m58s
CI / docker (push) Successful in 10s
CI / coverage (push) Successful in 13m49s
CI / status-check (push) Failing after 1s
CI / benchmark-publish (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled

This commit is contained in:
2026-04-16 21:58:11 -04:00
parent 5e3b4c9b68
commit 85c22aa7a8
3 changed files with 3 additions and 4 deletions
+1 -1
View File
@@ -40,7 +40,7 @@ permission:
"forgejo-label-manager": allow
skill:
"*": deny
"auto-agents-systems": allow
"auto-agents-system": allow
---
# PR Merge Supervisor
+1 -1
View File
@@ -38,7 +38,7 @@ permission:
"forgejo-label-manager": allow
skill:
"*": deny
"auto-agents-systems": allow
"auto-agents-system": allow
---
# PR Merge Worker
+1 -2
View File
@@ -61,8 +61,7 @@ You assess overall product completeness. You check all dimensions and return eit
9. **Documentation** — do README, API docs, and changelogs exist and appear current?
10. **Blockers** — are there zero issues with the `Blocked` label?
For the static checks (items 4 to 8 above) review the CI status on master if the other points are not passing (to save time). Only manually run these steps on the code locally
to verify when all other points are satisfied.
For the static checks (items 4 to 8 above) review the CI status on master as it is reported by Forgejo's CI system, do not run them locally. Also take a fail-fast approach, check the server and once you see at least one of these failing then just declare incomplete and return without checking the other points further.
## What You Return