docs: avoid direct shell interpolation of Codex output#24
Merged
Conversation
Route Codex output through an environment variable before printing it so examples do not splice generated text directly into a shell script.
Member
|
merged icoretech/codex-action#24 as 93e7597; added follow-up 4199454 for the existing README markdownlint spacing failure thanks for reporting and fixing this |
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
2 participants
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.
Summary
envbefore printing Codex output.run:script bodies.Why
GitHub expressions are expanded before the shell runs. Passing generated Codex output through an environment variable keeps the examples safer for multiline or shell-sensitive output and matches the pattern already used in other examples in this README.
Testing