Skip to content

Conversation

@iennae
Copy link
Contributor

@iennae iennae commented Jan 31, 2026

Description

checking impact of removing generated samples out of handwritten samples. generally snippet-gen generated samples should never be in handwritten repos.

Checklist

@iennae iennae requested review from a team as code owners January 31, 2026 00:30
@snippet-bot
Copy link

snippet-bot bot commented Jan 31, 2026

Here is the summary of changes.

You are about to delete 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 samples Issues that are directly related to samples. api: language Issues related to the Cloud Natural Language API API. labels Jan 31, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @iennae, 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 focuses on refining the sample code repository by removing specific auto-generated code snippets and their associated files. The primary goal is to ensure that generated samples are not mistakenly placed in directories meant for manually written code, thereby enhancing the overall structure and logical organization of the codebase.

Highlights

  • Sample Cleanup: Removed the language_sentiment_text.py sample, which was identified as a generated snippet, along with its corresponding test file and dependency lists.
  • Directory Organization: The removal addresses an organizational issue where generated samples were located within a directory structure potentially intended for handwritten code, improving clarity and maintainability.
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 removes several files related to an older, generated language_sentiment_text sample from the language/snippets/generated-samples/v1/ directory. The deleted files include the sample code, its test, and requirement files. This appears to be a cleanup of obsolete samples, as a more up-to-date version of the language_sentiment_text sample exists in language/v1/. The changes are straightforward and look correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: language Issues related to the Cloud Natural Language API API. samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant