test: restrict default runs to OpenAI credentials - #5277
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0333905c6b
ℹ️ 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".
Require explicit opt-in for external integration providers and exclude examples needing additional credentials from default auto runs. Update hosted DeepWiki examples and integration tests to use the current ask_wiki_question tool name.
0333905 to
0a4b9f4
Compare
markstuart-oai
left a comment
There was a problem hiding this comment.
Reviewed the complete diff at 0a4b9f4. Default integration runs clear inherited provider-enable flags and external keys before bootstrap/build, while explicit provider flags retain the intended routes. Collection deselects only unrequested external cases; OpenAI adapter coverage, custom example skip lists and the strict release checks remain intact. No actionable correctness or structural findings.
Validation: inspected the new regression tests and the existing runner/provider paths; all 24 exact-head hosted checks passed, including Linux/Windows tests and packaged-contract checks. Source-only review: no local tests or live provider/DeepWiki calls were run.
This pull request updates default example and integration runs to retain OpenAI-backed and credential-free coverage while requiring explicit execution for additional-credential providers. It also fixes DeepWiki calls after the server renamed
ask_questiontoask_wiki_question.