Skip to content

Update README.md#1995

Open
loosebazooka wants to merge 1 commit intomainfrom
loosebazooka-patch-1
Open

Update README.md#1995
loosebazooka wants to merge 1 commit intomainfrom
loosebazooka-patch-1

Conversation

@loosebazooka
Copy link
Member

No description provided.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @loosebazooka, 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 refining the README.md to ensure its content is current and clear. It removes obsolete information that could confuse users and streamlines the explanation of how to verify distroless images, enhancing the overall accuracy and readability of the documentation.

Highlights

  • Documentation Cleanup: Removed an outdated note regarding OCI manifest errors and the need to update container tooling, as this information is no longer current.
  • Cosign Verification Clarification: Simplified the description for cosign image verification by removing a time-sensitive statement about it being the 'only supported mechanism starting November 2023', making the documentation more evergreen.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • README.md
    • Removed a paragraph detailing OCI manifest changes from March 2023 and the recommendation to update container tooling.
    • Modified the 'How do I verify distroless images?' section to remove the phrase '-- this is the only supported mechanism starting November 2023', providing a more general statement about cosign verification.
Activity
  • No human activity has been recorded on this pull request yet.
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
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 updates the README.md file by removing outdated information. The changes are beneficial for keeping the documentation current. I have one suggestion to improve the phrasing in the image verification section for better clarity and conciseness.


All distroless images are signed by [cosign](https://github.com/sigstore/cosign) with ephemeral keys (keyless) -- this is the only supported mechanism starting November 2023.
We recommend verifying any distroless image you use before building your image. You can verify the keyless signature of any distroless image with:
All distroless images are signed by [cosign](https://github.com/sigstore/cosign) with ephemeral keys (keyless). We recommend verifying any distroless image you use before building your image. You can verify the keyless signature of any distroless image with:
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

For improved readability and conciseness, this sentence could be rephrased. The current version is a bit long and the repetition of "verify" could be avoided.

Suggested change
All distroless images are signed by [cosign](https://github.com/sigstore/cosign) with ephemeral keys (keyless). We recommend verifying any distroless image you use before building your image. You can verify the keyless signature of any distroless image with:
All distroless images are signed by [cosign](https://github.com/sigstore/cosign) with ephemeral keys (keyless). We recommend verifying any distroless image before use. To verify the keyless signature, run:

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🌳 🔧 Config Check

This pull request has not modified the root BUILD

@github-actions
Copy link
Contributor

github-actions bot commented Feb 3, 2026

🌳 🔄 Image Check
This pull request doesn't make any changes to the images. 👍
You can check the details in the report here

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.

1 participant