Move .agent to .agents

[christhompsongoogle]

Move .agent to .agents

[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 implements a minor refactoring by renaming the .agent directory to .agents. This change primarily aims to enhance clarity and align with standard pluralization conventions, potentially anticipating a future where multiple agents or agent-related configurations are managed within this directory.

Highlights

• Directory Renaming: The core directory for agent-related files has been renamed from .agent to .agents to improve naming consistency and reflect potential future expansion.

🧠 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/firebase_studio/migrate.ts
  • Updated the agentDir constant to reference the newly named .agents directory.

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 renames the .agent directory to .agents. However, the change is incomplete. A reference to the old directory name remains in the firebase.json configuration created by the createFirebaseConfigs function. This should be updated to ensure the new .agents directory is correctly ignored during deployments.

[gemini-code-assist]

While this directory name is updated correctly, a related reference in the createFirebaseConfigs function was missed. On line 348, the ignore list for apphosting in the generated firebase.json still refers to ".agent". Please update it to ".agents" to ensure the directory is correctly ignored during deployments.

[christhompsongoogle]

Fixed