Cloud deploy patterns

[yeshwanth1993]

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

• Tests pass
• Appropriate changes to documentation are included in the PR

[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 refines the GCP CI/CD design skill by expanding the scope of strategic consultation questions to better capture user requirements for advanced deployment strategies. It also introduces a new, detailed CI/CD pattern that outlines a trunk-based CI with tag-based continuous delivery using Google Cloud Deploy, providing a structured approach for controlled releases. Additionally, it standardizes the file extensions of existing pattern definitions to YAML for improved consistency and readability.

Highlights

• Enhanced Strategic Consultation: The SKILL.md document was updated to include more comprehensive strategic questions during the consultation phase, specifically adding considerations for rollback and canary deployments.
• New CI/CD Pattern Introduced: A new CI/CD pattern, pattern_trunk_based_ci_tag_based_cd.yaml, has been added. This pattern details a workflow where CI runs on every main branch push, and CD (including container build and Cloud Deploy release creation) is triggered by Git tags.
• File Extension Standardization: Existing CI/CD pattern files, pattern_git_tag_triggered_release.txt and pattern_trunk_based_push_to_deploy.txt, were renamed to use the .yaml extension for consistency.

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

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.

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 introduces a new CI/CD pattern for trunk-based development with tag-based releases and migrates existing patterns from .txt to .yaml format. The changes are well-structured. I've added a couple of suggestions to the new pattern definition file to improve naming consistency and the accuracy of its metadata.