Simplify maintainer CI approval note
All checks were successful
trusted-ci / check (pull_request_target) Successful in 2m23s
pr-policy / check (pull_request_target) Successful in 5s

This commit is contained in:
matamune 2026-05-20 22:37:28 +00:00
parent 7012f76ff6
commit 127735f90e
Signed by: matamune
GPG key ID: 3BB8E7D3B968A324

View file

@ -17,10 +17,10 @@ vp run release:check
Pull requests get a lightweight `pr-policy` check first. That check runs from
trusted target-branch code with `pull_request_target` and does not check out or
execute PR code. Full CI runs through the `trusted-ci` workflow after a
maintainer applies the one-shot `ci:run-full` label; the workflow consumes that
label before checking out the approved PR head, so new commits need another
maintainer run. PRs that change `.forgejo/workflows` need the
maintainer-applied `ci:reviewed-workflow` label before the policy check passes.
maintainer applies the `ci:run-full` label; if a PR gets new commits, remove
and reapply that label to approve another run for the new head. PRs that change
`.forgejo/workflows` need the maintainer-applied `ci:reviewed-workflow` label
before the policy check passes.
This is a Node 24 + pnpm + VitePlus monorepo. Keep changes scoped to the smallest package, app, flow,
or docs surface that solves the problem: