Skip to content

Fix spelling mistakes in Go comments#37617

Merged
jrmccluskey merged 1 commit intoapache:masterfrom
MansiSingh17:gsoc-first-pr
Feb 17, 2026
Merged

Fix spelling mistakes in Go comments#37617
jrmccluskey merged 1 commit intoapache:masterfrom
MansiSingh17:gsoc-first-pr

Conversation

@MansiSingh17
Copy link
Contributor

This PR fixes minor spelling mistakes in Go comments.

Changes:

  • recieve → receive
  • recieves → receives

No functional or behavioral changes.
This is my first contribution to Apache Beam.
Thank you for reviewing!

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @MansiSingh17, 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 focuses on improving code readability and consistency by rectifying minor spelling errors found in Go comments. The modifications are limited to documentation, ensuring that the codebase remains functionally identical while presenting more accurate and professional commentary.

Highlights

  • Spelling Corrections: Corrected common spelling mistakes ('recieve' to 'receive' and 'recieves' to 'receives') within Go comments across two files.
  • No Functional Changes: Ensured that these changes are purely cosmetic, affecting only comments and introducing no functional or behavioral alterations to the codebase.

🧠 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
  • sdks/go/pkg/beam/core/runtime/harness/datamgr.go
    • Corrected 'recieve' to 'receive' in a comment explaining data handling logic.
  • sdks/go/pkg/beam/runners/prism/internal/engine/teststream.go
    • Corrected 'recieves' to 'receives' in a comment for the TagsToPCollections function.
Activity
  • No review activity or comments have been recorded yet for this pull request.
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.

@github-actions
Copy link
Contributor

Assigning reviewers:

R: @jrmccluskey for label go.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

Copy link
Contributor

@jrmccluskey jrmccluskey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@jrmccluskey jrmccluskey merged commit e2a2b29 into apache:master Feb 17, 2026
13 checks passed
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