Repository navigation
ci: finish the Pullfrog timeout quest on DeepSeek V4.1 Flash - #7714
Conversation
Quest-Claim: 4f9e77bbc594cde6
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Pullfrog's OSS proxy already runs DeepSeek V4.1 Flash (the funded default, chosen server-side) and forces high effort, so the workflow's effort input was a no-op. Drop it, and delete the quest: a 135-file review now posts in 11 minutes, inside the one-hour run limit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Design change: the The maintainer decided on 2026-11-03 that effort can't be lowered (the OSS proxy forces high) and picked DeepSeek V4.1 Flash as the review model. Pullfrog's server already picks that model for this repo on the OSS route, and the workflow's (Written by Claude Opus 5.5) |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 4 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head 72665d4.
No actionable findings. The diff removes the finished quest and index entry without changing the workflow. The linked trial job completed successfully, and its log confirms the proxy model, high effort, and one-hour default described in the PR. Recording the server-selected default rather than adding an ignored workflow input is a reasonable direction.
Verification: GitHub-only static review of the quest diff and linked trial job/log. I did not independently reproduce the wider run sample or run CI.
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Delete the Pullfrog timeout quest — removes
quest/m0/ci/pullfrog-timeout.mdand its bullet inquest/m0/ci/README.md; the quest's stated goal (large reviews finish under the run limit) is recorded as met by the #7729 trial, with theeffort/timeoutinputs established as dead on the OSS route so no workflow edit is needed. - No workflow change —
pullfrog.ymlis unchanged frommain, matching the stated revert of the earliereffort: medium/timeout: 1hattempt. - No dangling references — no remaining links to
pullfrog-timeoutor the removed title anywhere in the tree, and the README list stays well-formed.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) | 𝕏

Problem
Pullfrog reviews were hitting the action's one-hour run limit on large PRs (41178266611, 41362378749, 41404718134, all at 60m+).
Approach
The quest finishes with no workflow change:
effort: mediumandtimeout: 1hto.github/workflows/pullfrog.yml. That change is reverted. Pullfrog's OSS proxy forces high effort (main.ts#L496), so the input did nothing.1his already the default.utils/runContext.tsproxyModel). The workflow'smodel:input is not "explicit" (utils/payload.ts#L385-L388), so on this route it is ignored (utils/modelAccess.ts, thenmain.tsclearsresolvedModelwhenproxyModelis set). DeepSeek Flash (deepseek/deepseek-flash) is the OSS-funded default (models.tsAUTO_TIER_TARGET). Every inspected run logsproxy: oss → openrouter/deepseek/deepseek-v4.1-flash, including the 10-31 and 11-02 timeouts. Runs since 2026-11-03 ~18:30Z log the dated pindeepseek-v4.1-flash-1017. Amodel:line in the workflow would be dead config, and it would fail if the repo ever left the OSS route without a DeepSeek key, so none is added.quest rmdeletes the quest and its link inquest/m0/ci/README.md.Trial
moq-dev/moq#7729 (135 files, +1055/−545):
pullfrog[bot]review posted at 23:29:11Z. That is 10m59s, under one hour.Run agenttook 11m41s (23:18:27Z to 23:30:08Z).openrouter/deepseek/deepseek-v4.1-flash-1017 (proxy), efforthigh, timeout1h (default).Wider sample from the Actions API (600 runs, 2026-11-01T17:35Z to 2026-11-03T23:30Z): the last run that took ≥55 minutes was 41404718134, at 2026-11-02 07:27Z. Of roughly 450 completed runs since then, none came close; the longest of the latest 93 took 35 minutes (a "Fix CI" run).
Decisions
✅ Effort (maintainer, 2026-11-03): Pullfrog forces high effort on the OSS route, so effort can't be lowered. This supersedes the earlier effort-first brief, so the
effort: mediuminput is dropped.Review model (maintainer, 2026-11-03, after asking for public rankings):
It was already Pullfrog's OSS default for this repo, chosen server-side. The repo needs no change, and nothing needs clicking in the Pullfrog console.
✅ Completion (maintainer, 2026-11-03): trial on one large PR and record a review under one hour. Met above, so the quest is deleted.
Impact
pullfrog.ymlis byte-identical tomain.Follow-ups
@moq/libav@0.1.0/ absent Nix setup error in Pullfrog's dependency install (41614007828) belongs to Claim the new npm names.Validation
actionlintandzizmor --offline --quiet .github: passed.quest check --base origin/main: passed (563 documents).git diff --check: passed.just cinot run (the brief says not to build); the diff againstmainonly deletes a quest and its link.Review
Local
quest review --new: Codex,gpt-6.1-sol, medium effort, round 1, reviewed head72665d431419ee243f42617ab1509c224cb855f7: no findings.(Written by Claude Opus 5.5)