Skip to content

docs: update Gemini model path from google_ai_studio to gemini in con… #1731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Apr 30, 2025
Merged

docs: update Gemini model path from google_ai_studio to gemini in con… #1731

merged 1 commit into from
Apr 30, 2025

Conversation

Yash-1511
Copy link
Contributor

@Yash-1511 Yash-1511 commented Apr 29, 2025 •
edited by qodo-merge-for-open-source bot
Loading

User description

This PR addresses the following improvements related to issue #1730:

  1. Documentation Update:
  • Corrects the Gemini provider name for LiteLLM from google_ai_studio to gemini in the usage guide (docs/docs/usage-guide/changing_a_model.md), ensuring consistency with the actual provider key used in code and LiteLLM documentation.

Motivation

  • The previous documentation referenced an outdated provider name, which could cause confusion for users integrating Gemini models via LiteLLM.

PR Type

Documentation

Description

  • Update Gemini provider name in usage guide documentation

  • Replace outdated google_ai_studio with correct gemini path

  • Ensure configuration examples match LiteLLM and code usage

Changes walkthrough 📝

Relevant files
Documentation
changing_a_model.md
Correct Gemini provider path in configuration documentation

docs/docs/usage-guide/changing_a_model.md

  • Changed configuration examples to use gemini/gemini-1.5-flash instead
    of google_ai_studio/gemini-1.5-flash
  • Updated both model and fallback_models example lines for accuracy
  • Ensured documentation aligns with actual provider key in code and
    LiteLLM docs
    		• +2/-2     
    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
    •

    @qodo-merge-for-open-source Qodo Merge for Open Source
    Copy link
    Contributor

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    🎫 Ticket compliance analysis 🔶

    1730 - Partially compliant

    Compliant requirements:

    • Update documentation to use "gemini" instead of "google_ai_studio" as the provider name for Gemini models
    • Ensure configuration examples match LiteLLM documentation and actual code usage

    Non-compliant requirements:

    • Consider adding a warning log for models not included in MAX_TOKENS

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    @qodo-merge-for-open-source Qodo Merge for Open Source
    Copy link
    Contributor

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    Learned
    best practice
    Align configuration section names

    The configuration section name in .secrets.toml should match the provider name
    used in the model path. Since the model path now uses gemini/, the secrets
    section should also be updated from [google_ai_studio] to [gemini] for
    consistency.

    docs/docs/usage-guide/changing_a_model.md [173-180]

     ```toml
 [config] # in configuration.toml
 model="gemini/gemini-1.5-flash"
 fallback_models=["gemini/gemini-1.5-flash"]
 
-[google_ai_studio] # in .secrets.toml
+[gemini] # in .secrets.toml
 gemini_api_key = "..."
    
- [ ] **Apply this suggestion** <!-- /improve --apply_suggestion=0 -->

<details><summary>Suggestion importance[1-10]: 6</summary>

</details></details></td><td align=center>Low

</td></tr>
<tr><td align="center" colspan="2">

- [ ] More <!-- /improve --more_suggestions=true -->

</td><td></td></tr></tbody></table>

- [ ]  **Author self-review**: I have reviewed the PR code suggestions, and addressed the relevant ones. <!-- fold suggestions self-review -->

    @Yash-1511 Yash-1511 mentioned this pull request Apr 29, 2025
    Closed
    @mrT23
    Copy link
    Collaborator

    mrT23 commented Apr 30, 2025

    cool, thanks

    @mrT23 mrT23 merged commit 14ad044 into qodo-ai:main Apr 30, 2025
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Reviewers

    @mrT23 mrT23 mrT23 approved these changes

    Assignees
    No one assigned
    Labels
    Review effort 1/5
    Projects
    None yet
    Milestone
    No milestone
    Development

    Successfully merging this pull request may close these issues.
    2 participants
    @Yash-1511 @mrT23