Skip to content

fix(packages): Remove QA registry destinations from image_copy_rules #640

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.

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

Merged
merged 1 commit into from
Jul 2, 2025

Conversation

wuhuizuo
Copy link
Contributor

We have migrated repositories from qa/* to pingcap/* and tikv/* for about 1 year.
It's time to remove the sync rules.

We have migrated repositories from `qa/*` to `pingcap/*` and `tikv/*`
for about 1 year.
It's time to remove the sync rules.
Copy link

ti-chi-bot bot commented Jun 19, 2025

I have already done a preliminary review for you, and I hope to help you do a better job.

Summary:
This pull request aims to remove QA registry destinations from image copy rules in the delivery.yaml file, following a repository migration. The approach involves deleting specific entries related to the hub.pingcap.net/qa/* repositories. Overall, the changes are straightforward and align with the goal of cleaning up outdated configurations.

Critical Issues:
None

Code Improvements:

  • File: packages/delivery.yaml
    • Lines 74-78, 80-84, 88-92, 94-98, 102-106, 108-112, 116-120, 122-126, 130-134, 136-140, 144-148, 150-154, 158-162, 164-168, 172-176, 178-182, 186-190, 192-196, 200-204, 206-210, 214-218, 220-224, 228-232, 234-238, 242-246, 248-252, 256-260, 262-266, 270-274, 276-280, 284-288, 290-294, 298-302, 304-308, 312-316, 318-322, 326-330, 332-336, 340-344, 346-350:
      • The repeated pattern of removing entries related to hub.pingcap.net/qa/* repositories suggests an opportunity for refactoring to avoid duplication. Consider extracting this common logic into a reusable function to enhance maintainability and reduce the chance of errors when making similar changes in the future.

Best Practices:

  • File: packages/delivery.yaml
    • Lines 72, 79, 87, 93, 101, 107, 115, 121, 129, 135, 143, 149, 157, 163, 171, 177, 185, 191, 199, 205, 213, 219, 227, 233, 241, 247, 255, 261, 269, 275, 283, 289, 297, 303, 311, 317, 325, 331, 339, 345:
      • Adding comments above each block of removed entries can improve code readability and provide context for future developers regarding the rationale behind these deletions. This documentation will help in understanding the history of the changes and why certain configurations were removed.

By implementing the suggested improvements, the codebase will become more maintainable, readable, and less error-prone, ensuring smoother transitions in the future.

@ti-chi-bot ti-chi-bot bot added the size/M label Jun 19, 2025
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.

Summary of Changes

Hello @wuhuizuo, 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 removes outdated QA registry destinations from the image copy rules, reflecting the completed migration of repositories to new locations. This cleanup ensures that images are no longer synced to the old QA registries, streamlining the image delivery process.

Highlights

  • Cleanup: Removed QA registry destinations from image_copy_rules in packages/delivery.yaml.
  • Migration Completion: This change finalizes the migration of repositories from qa/* to pingcap/* and tikv/*.
  • Image Sync Rules: Removed sync rules associated with the old QA registry destinations.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 successfully removes the outdated hub.pingcap.net/qa/* registry destinations from the image_copy_rules in packages/delivery.yaml, aligning with the migration mentioned in the description. The changes appear correct and consistent across the file. I've identified a couple of medium-severity maintainability points regarding potentially unused definitions as a result of these removals.

Copy link

@stevenayu stevenayu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link

ti-chi-bot bot commented Jul 2, 2025

@stevenayu: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@wuhuizuo
Copy link
Contributor Author

wuhuizuo commented Jul 2, 2025

/approve

Copy link

ti-chi-bot bot commented Jul 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stevenayu, wuhuizuo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Jul 2, 2025
@ti-chi-bot ti-chi-bot bot merged commit ed47b30 into main Jul 2, 2025
5 checks passed
@ti-chi-bot ti-chi-bot bot deleted the refactor/remove-sync-rule-to-qe/repo branch July 2, 2025 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants