Skip to content

Conversation

yeyuanyyg
Copy link

Continuous tuning accepts a model resource name as the base_model and an optional checkpoint ID to run continuous tuning from.

@yeyuanyyg yeyuanyyg requested review from a team as code owners October 3, 2025 18:11
Copy link

snippet-bot bot commented Oct 3, 2025

Here is the summary of changes.

You are about to add 1 region tag.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Oct 3, 2025
Copy link
Contributor

Summary of Changes

Hello @yeyuanyyg, 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 enhances the google-genai SDK samples by adding a new example for continuous tuning. This allows developers to fine-tune existing models from a specific checkpoint, enabling iterative model improvement and more efficient resource utilization for machine learning workflows.

Highlights

  • New Continuous Tuning Sample: Introduced genai/tuning/continuous_tuning_create.py to demonstrate creating continuous tuning jobs using the google-genai SDK.
  • API Usage: The new sample showcases how to use client.tunings.tune with base_model and pre_tuned_model_checkpoint_id for continuous tuning, including a polling mechanism to monitor job progress.
  • Dependency Update: The google-genai dependency in genai/tuning/requirements.txt has been updated to version 1.39.1.
  • Unit Test Coverage: A new test, test_continuous_tuning_create, was added to genai/tuning/test_tuning_examples.py to ensure the new continuous tuning functionality works as expected with mocked API responses.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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

  1. 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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 adds a new code sample for continuous tuning (continuous_tuning_create.py) and a corresponding test. The changes look good overall, but I have a few suggestions to improve the robustness of the new sample and its test. Specifically, I've pointed out a need for better error handling in the case of a failed tuning job, a minor clarification for a TODO comment, and a way to strengthen the new test to cover the job polling logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
samples Issues that are directly related to samples.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants