| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
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.
Customization To customize the 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 counterproductive. 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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
Changing Firebase Auth's Apple keychain access group clears an existing unshared user before Dart can retain it. This adds an opt-in migrateCurrentUser setting that captures the native user before switching access groups and restores it with updateCurrentUser, preserving existing sessions including anonymous users.
An iOS integration test verifies that an anonymous user's UID is preserved when moving to the test app's shared keychain access group.
Related Issues
Checklist
Breaking Change