Skip to content

Conversation

@bkendall
Copy link
Collaborator

No description provided.

ThadCastl3 and others added 13 commits July 21, 2025 11:46
…e your bill, such as minimum instances required.
Co-authored-by: Bryan Kendall <[email protected]>
…port for channel site deployment with force flag. Updated tests to and types to account for force flags. Force flag is now optional on ProductionDeployConfig and ChannelDeployConfig. Simplified deploy calls using force flag to automatically append force based on the boolean value nad removed the force-specific branch in index.ts
Co-authored-by: Jeff <[email protected]>
Copy link

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

Summary of Changes

Hello @bkendall, 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 updates the README.md file to introduce and document a new force option for Firebase deployments. This option, when enabled, utilizes the Firebase CLI's --force flag to automatically accept interactive prompts, thereby streamlining automated deployment workflows by bypassing manual confirmations.

Highlights

  • Documentation Update: The README.md file has been updated to include details about a new force option.
  • New force Option: This new boolean option allows users to leverage the Firebase CLI's --force flag, which automatically accepts all interactive prompts during deployment.
  • Usage Examples: Examples within the README.md now include commented-out lines demonstrating how to optionally add the force: true flag in Firebase deployment configurations for both preview and live channels.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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

@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 adds documentation for a new force input parameter for the Firebase Hosting GitHub Action. The changes include adding the force flag to the example workflows in the README and adding a new section to describe what the flag does. The implementation for this flag appears to be present in action.yml and the action's source code.

My review focuses on the clarity of the new documentation. I have one suggestion to make the description of the force flag more comprehensive and to include a word of caution, aligning it more closely with its definition in action.yml.


### `force` _{boolean}_

Uses the Firebase CLI's `--force` flag to automatically accept all interactive prompts.

Choose a reason for hiding this comment

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

medium

For clarity and to ensure users understand the impact of this option, consider expanding the description to be more aligned with the one in action.yml. Including a note of caution would be particularly helpful given the nature of the --force flag.

Suggested change
Uses the Firebase CLI's `--force` flag to automatically accept all interactive prompts.
Pass `true` to use the Firebase CLI's `--force` flag. This automatically accepts all interactive prompts during deployment. Use with caution.

@bkendall bkendall closed this Aug 18, 2025
@FirebaseExtended FirebaseExtended locked and limited conversation to collaborators Sep 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants