Skip to content

Conversation

@shunping
Copy link
Collaborator

@shunping shunping commented Dec 16, 2025

Prior to this PR, a new runner image was built and published via workflow https://github.com/apache/beam/actions/runs/20254703870.

The runner version in this image is 2.330.0 (https://github.com/actions/runner/releases/tag/v2.330.0).

addresses #37115

@shunping shunping requested a review from Abacn December 16, 2025 03:57
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @shunping, 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 maintaining the health and currency of the CI/CD infrastructure by updating the GitHub Actions self-hosted runner images. The update brings in the latest runner version 2.330.0, ensuring that automated workflows benefit from recent enhancements and bug fixes. Additionally, a small formatting inconsistency within the environment configuration was resolved.

Highlights

  • GitHub Actions Runner Image Update: The Docker image tag for GitHub Actions self-hosted runners has been updated across all configurations (main-runner, small-runner, highmem-runner, highmem-runner-22) to incorporate the latest runner version.
  • Runner Version 2.330.0: The new runner image now utilizes GitHub Actions runner version 2.330.0, bringing the CI/CD environment up to date with the latest features and stability improvements.
  • Configuration Whitespace Fix: A minor, cosmetic change was made to remove a trailing whitespace character from the 'ingress_domain' variable in the environment configuration file.
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.

@shunping
Copy link
Collaborator Author

r: @Abacn

@github-actions
Copy link
Contributor

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@shunping shunping merged commit 547ab60 into apache:master Dec 16, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants