Skip to content

Adjust caution note for firebase_options.dart#12995

Merged
sfshaza2 merged 4 commits intoflutter:mainfrom
nilsreichardt:patch-3
Mar 2, 2026
Merged

Adjust caution note for firebase_options.dart#12995
sfshaza2 merged 4 commits intoflutter:mainfrom
nilsreichardt:patch-3

Conversation

@nilsreichardt
Copy link
Contributor

It is safe to commit your firebase_options.dart to Git, see https://stackoverflow.com/a/37484053/8358501. To actually secure your app, see Firebase security checklist.

It is safe to commit your `firebase_options.dart` to Git, see https://stackoverflow.com/a/37484053/8358501. To actually secure your app, see [Firebase security checklist](https://firebase.google.com/support/guides/security-checklist).
@nilsreichardt nilsreichardt requested review from a team and sfshaza2 as code owners January 26, 2026 17:50
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @nilsreichardt, 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 documentation for the AI Toolkit by removing a misleading caution note. The note previously warned users not to commit firebase_options.dart to version control, but this file is generally safe to commit. The change aims to provide accurate guidance and prevent unnecessary confusion for developers, aligning the documentation with current best practices for Firebase projects.

Highlights

  • Documentation Correction: Removed an outdated caution note in src/content/ai/ai-toolkit/index.md that incorrectly advised against committing firebase_options.dart to Git.

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

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.

Copy link
Contributor

@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 correctly removes a misleading caution note about committing firebase_options.dart. The change is a good improvement to the documentation's accuracy. I've provided one suggestion to enhance this change by replacing the removed warning with a brief explanation of why it's safe to commit the file. This will provide more clarity for users and proactively address potential security concerns.

@nilsreichardt nilsreichardt marked this pull request as draft January 26, 2026 18:15
@nilsreichardt
Copy link
Contributor Author

Converted to draft because I'm not sure if flutterfire configure puts the Gemini API key into firebase_options.dart

@sfshaza2
Copy link
Contributor

Where are we on this, @nilsreichardt?

@nilsreichardt
Copy link
Contributor Author

Will come back in a few days 👍

…tion

Reintroduces a caution regarding the handling of `firebase_options.dart`. It advises against committing this file to public repositories if the app directly calls AI services from the client, and recommends routing requests through a backend service for production apps. Additionally, it emphasizes the importance of following the Firebase security checklist.
@nilsreichardt
Copy link
Contributor Author

/gemini review

@nilsreichardt nilsreichardt marked this pull request as ready for review February 28, 2026 19:35
Copy link
Contributor

@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 updates the security note regarding firebase_options.dart. The new note provides a more nuanced and accurate explanation of the security considerations, which is a significant improvement. I've added one suggestion to further enhance clarity by explicitly connecting the security advice to the code examples provided earlier in the document, which will help prevent potential confusion for developers.

@nilsreichardt nilsreichardt changed the title Remove caution note for firebase_options.dart Adjust caution note for firebase_options.dart Feb 28, 2026
@nilsreichardt
Copy link
Contributor Author

I clarified when you should not commit firebase_options.dart and that, for production apps, you should not call Vertix AI directly from a client.

@sfshaza2
Copy link
Contributor

sfshaza2 commented Mar 2, 2026

/gbcrun

@sfshaza2
Copy link
Contributor

sfshaza2 commented Mar 2, 2026

/gcbrun

@sfshaza2
Copy link
Contributor

sfshaza2 commented Mar 2, 2026

/gcbrun

@flutter-website-bot
Copy link
Collaborator

Visit the preview URL for this PR (updated for commit aac3e9f):

https://flutter-docs-prod--pr12995-patch-3-77gjo6gj.web.app

@sfshaza2 sfshaza2 merged commit 27de103 into flutter:main Mar 2, 2026
10 checks passed
@sfshaza2
Copy link
Contributor

sfshaza2 commented Mar 2, 2026

Thanks again, @nilsreichardt!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants