Migrate PR review to openrouter with pinned 0.11.0 action #13
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/issue-98-openrouter-review"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Migrates the wuming PR review to the openrouter backend with the fleet-standard two-tier model mapping (code/tests/performance on deepseek-v4-pro, security on kimi-k2-thinking, config/docs/shell on qwen3.7-flash) and pins the action to
0.11.0.Tracking: marvin8/wuming#98
WuMing
Found 1 issue(s). See inline comments below.
@ -11,3 +11,3 @@- uses: https://forge.marvin8.zone/marvin8/wuming@main- uses: https://forge.marvin8.zone/marvin8/wuming@0.11.0with:forgejo_token: ${{ forge.token }}config [HIGH]
References
${{ forge.token }}which is not a valid Actions context. Secret and variable accesses must use standard contexts such as${{ secrets.* }}or${{ vars.* }}. Correct the reference to match the actual configured secret name to prevent workflow failures.#13 (comment)
🔴 Pre-existing, untouched by this PR — and demonstrably functional:
forge.tokenis the token context provided by the forge.marvin8.zone runner (not standard GitHub contexts, but valid on this self-hosted instance). This PR's ownpr-reviewjob just executed successfully with that exact reference — the WuMing review that produced this finding was delivered through it. Replacing it withsecrets.*would break the workflow unless the secret were duplicated per repo.15a19a558e7b23f2cb0cWuMing
Found 1 issue(s). See inline comments below.
@ -15,1 +14,3 @@agents: config:deepseek-v4-flash,docs:deepseek-v4-flash,shell:deepseek-v4-flashopenrouter_key: ${{ secrets.wuming_openrouter_key }}backend: openrouteragents: config:qwen/qwen3.7-flash,docs:qwen/qwen3.7-flash,shell:qwen/qwen3.7-flashconfig [MEDIUM]
The value contains colons and commas without surrounding quotes. This can lead to YAML parsing ambiguity or incorrect interpretation as nested mappings. Wrap the entire string value in double quotes.
#13 (comment)
🔴 Not a defect — a plain YAML scalar containing colons (not followed by whitespace) and commas is valid in block context, and this exact line demonstrably parses and works: the file passed
yaml.safe_loadvalidation before commit, and this PR'spr-reviewjob executed end-to-end with thisagentsvalue — the review that produced this finding was delivered through it. The same unquoted style is used in wuming's ownci.ymland all fleet migration PRs.