Add custom API key support in AI configuration #454
Conversation
This file contains 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
|
Hey @swiftugandan , thanks for the contribution. Given that someone added gemini since you wrote this there are conflicts. Mind rebasing and fixing the merge conflicts? |
swiftugandan
force-pushed
the
support_apikey_for_custom_provider
branch
from
2969595 to
d4507fb
Compare
swiftugandan
force-pushed
the
support_apikey_for_custom_provider
branch
from
d4507fb to
950df6d
Compare
|
@nichochar rebase done |
|
Code LGTM, will test this locally and confirm it works, and if it does merge. Thanks! |
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.
This unlocks support for most open api compatible providers online