Skip to content

test(firestore): add integration tests for large documents#8367

Merged
dlarocque merged 9 commits into
mainfrom
dl/large-docs-tests
Jul 24, 2026
Merged

test(firestore): add integration tests for large documents#8367
dlarocque merged 9 commits into
mainfrom
dl/large-docs-tests

Conversation

@dlarocque

@dlarocque dlarocque commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Add integration tests for 16MB documents. Tests reads, writes, snapshot reads from server and the cache.

@gemini-code-assist

Copy link
Copy Markdown
Contributor
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 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.

@github-actions

Copy link
Copy Markdown
Contributor

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.

@dlarocque
dlarocque marked this pull request as ready for review July 23, 2026 13:36
@google-oss-bot

Copy link
Copy Markdown
Collaborator
1 Warning
⚠️ Did you forget to add a changelog entry? (Add the 'no-changelog' label to the PR to silence this warning.)

Generated by 🚫 Danger

@dlarocque
dlarocque requested a review from wu-hui July 23, 2026 14:57
@dlarocque
dlarocque merged commit 1b63d4a into main Jul 24, 2026
35 of 36 checks passed
@dlarocque
dlarocque deleted the dl/large-docs-tests branch July 24, 2026 18:01
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.

3 participants