Skip to content

chore(all): remove legacy configuration #13289

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
quartzmo merged 1 commit into from
Nov 3, 2025
Merged

chore(all): remove legacy configuration #13289

quartzmo merged 1 commit into from
Nov 3, 2025

Conversation

@jskeet
Copy link
Contributor

@jskeet jskeet commented Nov 3, 2025

These files are all obsolete after the Librarian migration.

@jskeet
chore(all): remove legacy configuration
de94b2f 
These files are all obsolete after the Librarian migration.
@jskeet jskeet requested a review from quartzmo November 3, 2025 11:22
@jskeet jskeet requested a review from a team as a code owner November 3, 2025 11:22
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Nov 3, 2025

Summary of Changes

Hello @jskeet, 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 significant cleanup by removing a suite of legacy configuration files. These files, which previously managed automated tasks such as OwlBot operations and Release Please workflows, have become obsolete due to a recent 'Librarian migration'. The change aims to streamline the repository's setup by eliminating outdated configurations.

Highlights

  • Removal of OwlBot Configuration: The .github/.OwlBot.lock.yaml and .github/.OwlBot.yaml files, which were used for OwlBot automation, have been removed as they are no longer needed.
  • Removal of Release Please Configuration: Several files related to Release Please, including .github/release-please.yml, .github/release-trigger.yml, and various release-please-manifest-*.json and release-please-config-*.json files, have been deleted.
  • Obsolete Files Post-Migration: All removed configuration files are now obsolete following a 'Librarian migration', indicating a successful transition to a new system or process for managing these aspects of the repository.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/new_client.yml
    • .github/workflows/owlbot_validation.yml
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. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Nov 3, 2025
View reviewed changes
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 legacy configuration files related to OwlBot and release-please. According to the description, these files are obsolete after the Librarian migration. The changes are straightforward and consist only of file deletions, which is appropriate for removing unused configuration. The pull request appears to be a clean and necessary housekeeping task.

@quartzmo quartzmo merged commit 6e77e86 into googleapis:main Nov 3, 2025
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@quartzmo quartzmo quartzmo approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jskeet @quartzmo