Improve the CLI commands ref

[joehan]

Description

Adding extra language to push agents toward init + deploy

[gemini-code-assist]

Summary of Changes

Hello @joehan, 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 clarity and structure of the Firebase App Hosting CLI command reference documentation. The primary goal is to guide users more effectively by distinguishing between general-purpose commands and those specifically intended for automated deployment setups, thereby preventing potential misuse and improving the overall user experience with the CLI.

Highlights

• Documentation Reorganization: The documentation for Firebase App Hosting CLI commands has been reordered to group related commands more logically.
• Clarity for CI/CD Commands: Specific commands related to automated deployments via GitHub (CI/CD), such as firebase apphosting:backends:create and firebase apphosting:rollouts:create, have been moved into a dedicated section.
• Usage Warning Added: An important warning has been added to clarify that CI/CD specific commands should only be used when setting up automated deployments via GitHub, and not for general firebase deploy workflows.

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

Changelog

• skills/firebase-app-hosting-basics/references/cli_commands.md
  • Added blank lines around ### headers for improved readability.
  • Relocated firebase apphosting:backends:create and firebase apphosting:rollouts:create commands to a new section titled 'Automated deployment via GitHub (CI/CD)'.
  • Introduced an 'IMPORTANT' note before the CI/CD commands to explicitly state their intended use case and warn against using them with firebase deploy.

Activity

• No specific activity (comments, reviews, progress) has been recorded for this pull request yet.

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 improves the clarity of the CLI commands reference by grouping commands related to automated GitHub deployments under a new section. This restructuring, along with the added warning, helps users distinguish between deployment methods. I've made a couple of suggestions to further improve the markdown formatting and structure.

[gemini-code-assist]

This line adds trailing whitespace at the end of the file, and the file is missing a final newline. This should be removed to ensure clean file formatting. It's also a good practice for text files to end with a single newline character on the last line of content.