Move apptesting:execute out from behind apptesting experiment

[lfkellogg]

This is in preparation for final testing and release of this feature.

Before:

$ firebase apptesting:execute
Error: apptesting:execute is not a Firebase command

After:

$ firebase apptesting:execute
error: missing required argument 'release-binary-file'

[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 makes the apptesting:execute command accessible to all users by removing its dependency on an experimental feature flag. This change is a preparatory step for the final testing and release of this feature, ensuring that the command can be invoked without needing to enable specific experiments.

Highlights

• Command Availability: The apptesting:execute command has been moved out from behind the apptesting experiment flag, making it generally available for all users.
• Experiment Flag Removal: The code registering the apptesting:execute command is no longer conditional on the experiments.isEnabled("apptesting") check.

🧠 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

• src/commands/index.ts
  • Moved the registration of the apptesting:execute command outside the experimental feature flag condition.

Activity

• No specific activity (comments, reviews, etc.) 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 moves the apptesting:execute command out from behind the apptesting experiment flag, making it generally available while keeping the apptesting:wata command experimental. The change in src/commands/index.ts is straightforward and correctly implements this logic, following existing patterns in the file for command registration. The implementation looks good and achieves the goal described.