Using the GEMINI_API_KEY
by default instead of the GOOGLE_API_KEY
one
#418
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.
Description of the change
Instead of using the
GOOGLE_API_KEY
by default, we're checking for theGEMINI_API_KEY
ones first since its naming is less misleading. TheGOOGLE_API_KEY
is still kept for consistency.Motivation
The Google API key can be misleading since it's not really an overall key for all of Google API and only for the Gemini ones.
Type of change
Choose one: Feature request
Checklist
git pull --rebase upstream main
).