Skip to content

dataconnect(docs): Fix BoM version noted in the docs for when realtime support was added to 34.14.0 (was 34.13.0)#8237

Merged
dconeybe merged 1 commit into
mainfrom
dconeybe/dataconnect/BomDocFix
May 30, 2026
Merged

dataconnect(docs): Fix BoM version noted in the docs for when realtime support was added to 34.14.0 (was 34.13.0)#8237
dconeybe merged 1 commit into
mainfrom
dconeybe/dataconnect/BomDocFix

Conversation

@dconeybe
Copy link
Copy Markdown
Contributor

No description provided.

…e support was added to 34.14.0 (was 34.13.0)
@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.

@dconeybe dconeybe marked this pull request as ready for review May 30, 2026 02:32
@dconeybe dconeybe merged commit c80152f into main May 30, 2026
52 checks passed
@dconeybe dconeybe deleted the dconeybe/dataconnect/BomDocFix branch May 30, 2026 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants