4f7de670f5
Some checks are pending
CI (PR) / scope (pull_request) Successful in 35s
CI (PR) / lint (pull_request) Successful in 45s
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 54s
CI (PR) / typecheck (pull_request) Successful in 31s
CI (PR) / knip (pull_request) Successful in 32s
CI (PR) / cycles (pull_request) Successful in 32s
CI (PR) / unit (pull_request) Successful in 55s
CI (PR) / int (pull_request) Successful in 2m46s
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
CI / deploy homeserver (teqo-1313) (push) Blocked by required conditions
CI / static (push) Waiting to run
CI / int (push) Waiting to run
CI / build (push) Waiting to run
CI / e2e (1) (push) Waiting to run
CI / e2e (2) (push) Waiting to run
CI / checks (push) Blocked by required conditions
PR Ready + auto-merge / ready-automerge (pull_request) Successful in 21m31s
Main merge flips claimed issues to done + in-prod / issue-done (pull_request) Successful in 12s
Promote plan-issue Related on main merge / plan-issue-ready (pull_request) Has been skipped
Agent pool supervisor / tick (pull_request) Successful in 28s
O merge POST faz um push para main; o hook pre-receive do Forgejo rejeita o push quando o usuário do token não tem write no repo — o GITHUB_TOKEN nativo age como o usuário sistema do Actions. Por isso nenhum auto-merge funcionou (o CLI morria no 409; runs 'success' eram leituras de PR já mergeada manualmente). O workflow do safety net agora injeta o mesmo PAT dos pós-merge. |
||
|---|---|---|
| .. | ||
| agent-pool.yml | ||
| agent-pr-ready-automerge.yml | ||
| archive-cursor-agent.yml | ||
| ci-pr.yml | ||
| ci.yml | ||
| issue-done-on-main-merge.yml | ||
| plan-issue-ready-on-main-merge.yml | ||