Repository navigation
chore: use the default model of Codex for update fixes and reviews - #26
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stops pinning the models that the update script runs Codex with, so the fixer and the reviewer use the default model of the Codex CLI and move to a new model when Codex does.
CODEX_MODELandREVIEW_MODEL.scripts/ai_fix.tsonly passes--modelto the reviewer whenREVIEW_MODELis set, as it already did for the fixer withCODEX_MODEL.The fixer and the reviewer now run the same model. The reviewer is still a session of its own that does not have the context of the fixer. Setting either variable in the workflow pins that stage again.