migrate to patch both

[mattKorwel]

i wanted to ensure we don't miss any patches.

/patch - does stable and preview
/patch both - does them both explicitly
/patch stable - just stable
/patch preview - just preview

[gemini-code-assist]

Summary of Changes

Hello @mattKorwel, 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 documentation for the /patch command, which maintainers utilize to create patch pull requests. The updates aim to provide clearer and more explicit control over which release channels (stable, preview, or both) are targeted when applying patches, thereby ensuring that no critical patches are inadvertently overlooked.

Highlights

• Updated /patch Command Syntax: The documentation for the /patch command has been revised to clarify its usage and options for maintainers.
• Default Patching Behavior: The /patch command, when used without specifying a channel, now defaults to patching both stable and preview channels.
• Explicit both Option: A new both option has been introduced for the /patch command, allowing maintainers to explicitly target both stable and preview channels.
• Channel-Specific Patching: The stable and preview options for the /patch command now exclusively patch their respective channels, removing the previous implicit dual-channel patching behavior for stable.
• Documentation Clarification: A previous note explaining that /patch stable would run twice for both channels has been removed, reflecting the updated and more explicit command behavior.

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

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 for the /patch command to reflect its new behavior, where it defaults to patching both stable and preview channels. The changes are mostly correct, but the documentation for the --dry-run flag was accidentally removed. I've added a comment to restore it, as it's an important feature for safely testing releases.

[gemini-code-assist]

The documentation for the --dry-run option has been removed in this change. Based on the provided context files, this feature still exists and is critical for testing releases safely. It should be included in the documentation. The command format should be updated to include it, and the explanation and examples should be restored.

Suggested change

	`/patch [channel]`
	- **channel**: `stable` or `preview`
	- **--dry-run** (optional): If included, the workflow will run in dry-run mode. This will create the PR with "[DRY RUN]" in the title, and merging it will trigger a dry run of the final release, so nothing is actually published.
	- **channel** (optional):
	- _no channel_ - patches both stable and preview channels (default, recommended for most fixes)
	- `both` - patches both stable and preview channels (same as default)
	- `stable` - patches only the stable channel
	- `preview` - patches only the preview channel
	Example: `/patch stable --dry-run`
	Examples:
	- `/patch` (patches both stable and preview - default)
	- `/patch both` (patches both stable and preview - explicit)
	- `/patch stable` (patches only stable)
	- `/patch preview` (patches only preview)
	`/patch [channel] [--dry-run]`
	- **channel** (optional):
	- _no channel_ - patches both stable and preview channels (default, recommended for most fixes)
	- `both` - patches both stable and preview channels (same as default)
	- `stable` - patches only the stable channel
	- `preview` - patches only the preview channel
	- **--dry-run** (optional): If included, the workflow will run in dry-run mode. This will create the PR with "[DRY RUN]" in the title, and merging it will trigger a dry run of the final release, so nothing is actually published.
	Examples:
	- `/patch` (patches both stable and preview - default)
	- `/patch both --dry-run` (dry run for both stable and preview - explicit)
	- `/patch stable` (patches only stable)
	- `/patch preview --dry-run` (dry run for preview only)

[github-actions]

Size Change: -2 B (0%)

Total Size: 17.3 MB

ℹ️ View Unchanged

Filename	Size	Change
./bundle/gemini.js	17.3 MB	-2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb	1.03 kB	0 B
./bundle/sandbox-macos-permissive-open.sb	830 B	0 B
./bundle/sandbox-macos-permissive-proxied.sb	1.31 kB	0 B
./bundle/sandbox-macos-restrictive-closed.sb	3.29 kB	0 B
./bundle/sandbox-macos-restrictive-open.sb	3.36 kB	0 B
./bundle/sandbox-macos-restrictive-proxied.sb	3.56 kB	0 B

_{compressed-size-action}