Repository navigation
fix: reject unsupported custom template options - #188
Merged
Merged
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. |
chenjiahan
added this pull request to stack #189
October 18, 2026 08:48
chenjiahan
force-pushed
the
chenjiahan/fix-custom-template-options
branch
2 times, most recently
from
October 18, 2026 08:54
a1f64fb to
633f6d6
Compare
chenjiahan
force-pushed
the
chenjiahan/fix-custom-template-options
branch
from
October 18, 2026 08:58
633f6d6 to
7b5d436
Compare
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
1 participant
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.
Custom templates bypass the toolkit's built-in setup, so silently accepting
--tools,--skill, or--template-versionwould leave users expecting configuration that was never applied.Reject these options before invoking the template's
createfunction and report all unsupported flags. String templates keep their existing behavior.