Add GitHub issue triage model flow#109
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bf7880e38
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| include_reasoning: opts.settings.triageReasoningEffort !== 'none', | ||
| reasoning: { | ||
| effort: normalizeOpenRouterReasoningEffort(opts.settings.triageReasoningEffort, model), | ||
| }, |
There was a problem hiding this comment.
Compute OpenRouter reasoning flag from effective effort
When triage uses OpenRouter, include_reasoning is based on the raw setting while reasoning.effort is normalized per model. For models where non-none settings are coerced to none (for example qwen/qwen3-coder:free), this sends a contradictory request (include_reasoning: true with effective effort none), which can trigger avoidable API errors or unexpected behavior. The non-triage OpenRouter provider already derives include_reasoning from the normalized effort, so this path should do the same.
Useful? React with 👍 / 👎.
Summary
Verification