404ac7ffe0
Some checks failed
Agent pool supervisor / tick (pull_request) Has been skipped
Main merge flips claimed issues to done + in-prod / issue-done (pull_request) Has been skipped
Promote plan-issue Related on main merge / plan-issue-ready (pull_request) Has been skipped
CI (PR) / scope (pull_request) Successful in 31s
CI (PR) / lint (pull_request) Successful in 41s
CI (PR) / docs-guards (pull_request) Successful in 8s
CI (PR) / plans-only-closes (pull_request) Successful in 7s
CI (PR) / format (pull_request) Successful in 50s
CI (PR) / typecheck (pull_request) Successful in 31s
CI (PR) / knip (pull_request) Successful in 30s
CI (PR) / cycles (pull_request) Successful in 30s
CI (PR) / unit (pull_request) Successful in 47s
CI (PR) / int (pull_request) Successful in 1m48s
CI (PR) / build (pull_request) Has been skipped
CI (PR) / e2e (1) (pull_request) Has been skipped
CI (PR) / e2e (2) (pull_request) Has been skipped
CI (PR) / checks (pull_request) Successful in 1s
PR Ready + auto-merge / ready-automerge (pull_request) Failing after 7m58s
O Forgejo posta o status do próprio job do safety net como pending durante o run inteiro: o gate antigo (pending.length === 0) era insatisfazível e o CLI nunca auto-mergeou nada — todo merge Forgejo até aqui foi manual (merged_by do dono), inclusive a PR #52 com CI vermelho (narrativa da 'raça' corrigida). O gate é: rollup CI (PR) / checks presente+verde (cascata inteira assentou), ignorando o contexto do próprio workflow; mergeable false só após assentar. |
||
|---|---|---|
| .. | ||
| e2e | ||
| fixtures | ||
| helpers | ||
| int | ||
| unit | ||