-
Notifications
You must be signed in to change notification settings - Fork 627
Remove the firebase-vertexai module #7202
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
… is no longer needed.
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
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.
Summary of Changes
Hello @davidmotson, 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!
This pull request performs a comprehensive removal of the firebase-vertexai
module from the project. This action is taken because the module is no longer required, suggesting a strategic shift in the project's architecture or the services it supports, likely in favor of the firebase-ai
SDK as indicated by previous deprecation notices.
Highlights
- Module Removal: The
firebase-vertexai
module, including all its source code, build configurations, documentation, and test files, has been entirely deleted from the repository. - Build System Integration: References to
firebase-vertexai
have been systematically removed from project-wide configuration files, such as the mainREADME.md
, CI/CD scripts (clean.py
), Gradle publishing plugins, and the overall list of subprojects (subprojects.cfg
). - Release Process Cleanup: The module's presence in the Bill of Materials (BOM) and GMaven index test data has also been purged, ensuring its complete eradication from the build and release pipelines.
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 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 or fill out our survey 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.
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
This pull request removes the firebase-vertexai
module. The changes primarily consist of deleting the module's directory and updating configuration files (README.md
, ci/fireci/fireciplugins/clean.py
, plugins/...
, subprojects.cfg
) to remove all references to it. The changes appear to be correct and consistent with the goal of removing the module. I have reviewed the modifications and did not find any issues.
plugins test results67 tests 67 ✅ 1m 29s ⏱️ Results for commit fae9434. ♻️ This comment has been updated with latest results. |
Size Report 1Affected ProductsNo changes between base commit (09dc310) and merge commit (6e50f8b).Test Logs |
Coverage Report 1Affected Products
Test Logs |
This module is no longer needed, so it's being removed.