Skip to content

Conversation

@elelaysh
Copy link

@elelaysh elelaysh commented Dec 3, 2025

sources added: HighAvailability (9.7 only) and SIG security common (common to all 9.X)

@elelaysh elelaysh requested a review from a team as a code owner December 3, 2025 09:09
@gemini-code-assist
Copy link

Summary of Changes

Hello @elelaysh, 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 updates the repository configurations to integrate Rocky Linux 9.7, replacing the older 9.6 versions which are now marked as deprecated. Additionally, it expands the available source repositories by including HighAvailability for 9.7 and the SIG Security Common for Rocky Linux 9, ensuring comprehensive package management.

Highlights

  • Rocky Linux 9.7 Repositories: All existing Rocky Linux 9.6 repositories (AppStream, BaseOS, Extras, CRB, HighAvailability) have been updated to their 9.7 counterparts across all architectures (x86_64, aarch64, and source).
  • Rocky Linux 9.6 Deprecation: The previous Rocky Linux 9.6 repositories have been formally moved to the deprecated list, indicating their end-of-life status.
  • New Source Repositories: Added source repositories for Rocky Linux 9.7 HighAvailability and Rocky Linux 9 SIG Security Common.
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

@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 updates the Rocky Linux repositories from version 9.6 to 9.7, moves the 9.6 repositories to the deprecated list, and adds new source repositories for HighAvailability and SIG Security. The changes are mostly correct, but I've found a path inconsistency for the HighAvailability repositories that could cause synchronization to fail. I've provided suggestions to fix this in both the active and deprecated repository files.

sources added: HighAvailability and SIG security common
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