Updated exit codes with clearer message. #401
Closed
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.
This PR improves error handling by providing more specific error messages based on the exit code from the Gemini CLI.
Previously, the action would exit with a generic "Gemini CLI execution failed" message. This change introduces a case statement that maps common exit codes to user-friendly messages, making it easier to diagnose the root cause of a failure. The action now also exits with the original exit code from the Gemini CLI, which can be useful for scripting and automation.
For example, a failure due to an invalid API key will now produce the message: "Gemini CLI execution failed (Authentication failure. Please check your credentials (API key or Google Cloud auth))" and exit with code 41.
Related Issue #217