docs: prefer GitHub native attestations over slsa-verifier

[CybotTM]

Summary

• Add "Using GitHub Attestations (Recommended)" section to SECURITY.md.template before the existing slsa-verifier instructions — gh attestation verify is simpler and natively supported
• Rename existing slsa-verifier section to "Using slsa-verifier (Legacy)" to signal deprecation
• Add immutable releases warning to security-config.md under the SLSA Generator Pinning Exception section

Test plan

• Verify SECURITY.md.template renders correctly with both verification methods
• Confirm the immutable releases note in security-config.md is visible under the SLSA section

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 project's security documentation to streamline release verification processes. It introduces a preference for GitHub's native attestation verification method, making it the recommended approach, while clearly marking the slsa-verifier method as legacy. Additionally, it enhances security configuration guidance by adding a crucial note about the immutability of GitHub releases, advising against deleting and recreating releases to fix provenance issues.

Highlights

• GitHub Attestations: Introduced a new "Using GitHub Attestations (Recommended)" section in SECURITY.md.template to guide users towards GitHub's native attestation verification.
• slsa-verifier Documentation: Renamed the existing slsa-verifier instructions in SECURITY.md.template to "Using slsa-verifier (Legacy)" to indicate its deprecation in favor of GitHub native attestations.
• Immutable Releases Warning: Added a warning about immutable GitHub releases to security-config.md under the SLSA Generator Pinning Exception section.

Changelog

• skills/github-project/assets/SECURITY.md.template
  • Added a new section titled "Using GitHub Attestations (Recommended)" with example gh attestation verify commands.
  • Renamed the previous "Binary Verification" section to "Using slsa-verifier (Legacy)".
• skills/github-project/references/security-config.md
  • Inserted a warning block about immutable GitHub releases and best practices for managing release provenance.

Activity

• The author outlined a test plan to verify the correct rendering of SECURITY.md.template for both verification methods and the visibility of the immutable releases note in security-config.md.

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. ↩

[gemini-code-assist]

Code Review

This pull request updates the documentation to recommend GitHub's native attestations for release verification over slsa-verifier. The changes in SECURITY.md.template are clear and introduce the new recommended method while marking the old one as legacy. I've added one suggestion to security-config.md to clarify the reasoning behind treating releases as immutable, as the current explanation about tags being 'permanently locked' is not strictly accurate.

[Copilot]

Pull request overview

Updates the GitHub Project skill’s security documentation to recommend GitHub CLI’s native attestation verification workflow ahead of the legacy slsa-verifier flow, and adds an additional note under the SLSA pinning exception guidance.

Changes:

• Add a “Using GitHub Attestations (Recommended)” verification section to SECURITY.md.template.
• Rename the existing SLSA verifier instructions to “Using slsa-verifier (Legacy)”.
• Add an “Immutable releases” warning under the SLSA Generator Pinning Exception in security-config.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
skills/github-project/references/security-config.md	Adds a cautionary note under the SLSA generator pinning exception section.
skills/github-project/assets/SECURITY.md.template	Adds GitHub attestation verification instructions and relabels slsa-verifier instructions as legacy.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.