Files
gatekeep/docs/dogfood.md
T
layue13 c6c2d071fb
Gatekeep evals / eval-floor (push) Successful in 3s
Gatekeep evals / eval-floor (pull_request) Successful in 15s
Gatekeep / gatekeep (pull_request) Failing after 1m46s
fix: harden partial 429 success, fallbacks, zh errors
Retry HTTP 429 with backoff; keep models beyond first 3 as
fallbacks; degrade agreement when some models fail; force-high
risk only if zero usable responses. Clearer zh-CN errors/docs for
dogfood uses: ./ rebase + workflow_dispatch re-run.
2026-10-27 08:35:52 +00:00

1.5 KiB
Raw Blame History

Dogfood — Gatekeep reviews Gatekeep

The Action repo itself runs Gatekeep on its own pull requests.

Piece Path / value
Live workflow .github/workflows/gatekeep-pr.yml
Action uses: ./ (repo-root action.yml)
Secret OPENROUTER_API_KEY → step env
Trigger pull_request (non-draft) + workflow_dispatch
Proven PR #2 got <!-- gatekeep-review -->; run 15833 success
Report language defaults/providers.yaml → language: zh-CN (override with Action language:)

Gitea notes: no actions/setup-node mirror — Action requires runner Node ≥18. PyYAML installs via workspace venv (PEP 668). Free OpenRouter models may 429: Action retries with backoff, tries fallback_models (list entries after the first 3), and only force-elevates risk to high when zero models succeed. Summary is Chinese when language: zh-CN.

How to see a review

  1. Branch off current main (or merge/rebase main into the PR branch — uses: ./ loads Action code from the PR head)
  2. Open/push a PR on https://git.potatolab.uk/layue13/gatekeep
  3. Wait for the Gatekeep workflow (same Actions runner pool as other layue13 repos)
  4. Look for the summary comment <!-- gatekeep-review --> (updated in place on re-run)
  5. Manual re-run: Actions → Gatekeep → Run workflow (workflow_dispatch), or push another commit

Consumer sample workflows remain under top-level workflows/ for copy-paste into other repos’ .github/workflows/.