feat(comment): update issue or PR comment with API key error #435
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.
Closes #434
Applied changes based on Issue #434.
I’ve added logic to the top‑level run() in src/main.ts so that when the OpenAI key check fails, we not only
core.setFailed(...)
but also try to post that same error message as a GitHub comment on the triggering issue/PR. Any failures to post the comment are caught and logged as errors, so they won’t mask the original failure. Specifically:postComment
alongsideprocessEvent
.postComment(config.octokit, config.repo, processedEvent.agentEvent.github, failureMessage)
, and wrapped that in its own try/catch.【F:src/main.ts†L34-L53】
These minimal changes ensure that an invalid
OPENAI_API_KEY
not only fails the Action but also surfaces the error back into the GitHub conversation.