Add skip_github_release option to Manual Release.

[scidomino]

TLDR

Adds an option to skip creating a github release.

Dive Deeper

For manual test releases we probably don't want to do a github release.

Reviewer Test Plan

I tested this manually.

[gemini-code-assist]

Summary of Changes

Hello @scidomino, 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 enhances the publish-release GitHub Action by adding a new configuration option to bypass the creation of a GitHub release. This provides increased flexibility for release workflows, especially for scenarios like manual test releases where a formal GitHub release might not be necessary or desired.

Highlights

• New Input Added: Introduced a new boolean input named skip_github_release to the publish-release GitHub Action, allowing users to explicitly control whether a GitHub release is created. This input defaults to false.
• Conditional Release Creation: Modified the 'Create GitHub Release' step within the action to incorporate the new skip_github_release input. The release will now only be created if dry-run is false AND skip_github_release is also false.

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 introduces a skip_github_release option to the publish-release action, allowing the GitHub release creation step to be skipped. The implementation is straightforward, but I have a couple of suggestions to improve consistency and correctness in the action's YAML definition. Specifically, I recommend aligning the new input's name with the existing kebab-case convention and using direct boolean evaluation in the conditional logic for if statements.

[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}

[richieforeman]

LG (pending comments)

[mattKorwel]

Honestly, we should also have a no channel option. if i'm pushing v0.0.11111 it really doesn't need the dev channel tag. doesn't have to block here though.