-
Notifications
You must be signed in to change notification settings - Fork 6.5k
fix: Remove reference to Gemini 1.5 #13338
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @holtskinner, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
This pull request addresses an outdated reference to the Gemini 1.5 model within the sample_configuration.json
file. The change replaces the string gemini-1.5-flash-001
with gemini-2.0-flash-001
, ensuring the configuration file points to the correct target model.
Highlights
- Model Update: The primary change involves updating the
target_model
field insample_configuration.json
fromgemini-1.5-flash-001
togemini-2.0-flash-001
.
Changelog
- generative_ai/prompts/test_resources/sample_configuration.json
- Updated the
target_model
value fromgemini-1.5-flash-001
togemini-2.0-flash-001
on line 5.
- Updated the
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
A model's name,
Updated for the future's game,
New version takes hold.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request updates the target model in the sample configuration file. The change seems straightforward, but let's ensure it aligns with the intended functionality and doesn't introduce any unintended consequences.
Summary of Findings
- Model Availability: Ensure that
gemini-2.0-flash-001
is a valid and available model for the project. If the model is not available, the prompt optimizer will fail.
Merge Readiness
The pull request seems straightforward and addresses the intended change. However, it's crucial to verify that the new model gemini-2.0-flash-001
is indeed the correct and available model. I am unable to approve this pull request, and recommend that users have others review and approve this code before merging.
No description provided.