chore: prepare Codex home directory and update API key parameter format#510
Merged
chore: prepare Codex home directory and update API key parameter format#510
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Jira-to-Codex GitHub Actions workflow to use a dedicated Codex “home” directory under the runner temp directory and switches the Codex action input for the API key to the newer hyphenated parameter name.
Changes:
- Add a step to create a Codex home directory at
${RUNNER_TEMP}/codex-home. - Update Codex action input from
openai_api_keytoopenai-api-key. - Pass the new
codex-homeinput to the Codex action.
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.
Why
This PR addresses the following problem / context:
How
Implementation summary - the following was changed / added / removed:
Notes
Any special considerations, workarounds, or follow-up work to note?