layue13
05f8fad38a
Gatekeep evals / eval-floor (push) Successful in 8s
Add .github/workflows/gatekeep-pr.yml with uses: ./ and OPENROUTER_API_KEY from secrets. Forge-agnostic API helper for Gitea.
1.5 KiB
1.5 KiB
Summary
Testing notes
- Discovered build/test entry points run locally or in CI (paste command / job link)
- Benchmarks vs thresholds (fps / startup / memory) if behavior-sensitive — or N/A
- Client-visible paths: noted if not verified on GitHub-hosted runners
Commands / evidence:
<!-- e.g. npm test, make verify, artifact URL from gatekeep-last-good-* -->
Risk (author hint — Gatekeep may raise the PR tier)
Author self-assessment (optional): low / medium / high
Sensitive paths touched? (auth, billing, .github/workflows, secrets, release): yes / no
How to revert
Rollback speed is the load-bearing wall. Fill this in before merge.
- One-step revert:
git revert <merge-sha>(or GitHub "Revert") then merge the revert PR. - Artifact / slot rollback: point
activeat previous known-good artifact (see Gatekeep deploy-slots note); restart. - Feature flag / kill switch:
- Data / world migrations:
- Owner if this causes an incident:
If this change is hard to revert, treat it as high risk and get the required human approvals.