-
Notifications
You must be signed in to change notification settings - Fork 32
feat(librarian): allow update-image to be a no-op #2807
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
base: main
Are you sure you want to change the base?
Conversation
The update-image command is really useful for container authors, in terms of checking performance, behavior, and configuration. It's useful to be able to run it even without a new image - because if everything is in a steady state, we shouldn't see any changes at all.
Summary of ChangesHello @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 enhances the Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this 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 modifies the update-image command to allow it to run even when there is no new container image, which is useful for diagnostic purposes. The change correctly removes the early exit when the image is unchanged, allowing the regeneration process to proceed. The corresponding tests have been updated to reflect this new behavior, ensuring that regeneration is now expected and verified in the no-change scenario. The implementation is straightforward and correct.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2807 +/- ##
==========================================
- Coverage 86.50% 86.50% -0.01%
==========================================
Files 120 120
Lines 10232 10231 -1
==========================================
- Hits 8851 8850 -1
Misses 977 977
Partials 404 404 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
The update-image command is really useful for container authors, in terms of checking performance, behavior, and configuration. It's useful to be able to run it even without a new image - because if everything is in a steady state, we shouldn't see any changes at all.
We still log that the image is the same, but don't count it as an error.