Skip to content

SCPBlocks: fix 'occured' -> 'occurred' in doc comment#382

Closed
SAY-5 wants to merge 1 commit into
stripe:masterfrom
SAY-5:fix-scpblocks-occured-typo
Closed

SCPBlocks: fix 'occured' -> 'occurred' in doc comment#382
SAY-5 wants to merge 1 commit into
stripe:masterfrom
SAY-5:fix-scpblocks-occured-typo

Conversation

@SAY-5
Copy link
Copy Markdown

@SAY-5 SAY-5 commented Apr 16, 2026

Doc comment in PublicHeaders/SCPBlocks.h line 63 reads no error occured. Fixed to occurred. Comment-only change.

The generated docs (docs/) will be regenerated from the source on next build, so fixing this header propagates to all versions of the HTML documentation.

Doc comment in PublicHeaders/SCPBlocks.h line 63 read 'no error occured'. Fixed to 'occurred'. Comment-only change.

Signed-off-by: SAY-5 <SAY-5@users.noreply.github.com>
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Apr 16, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

2 similar comments
@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Apr 16, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@cla-assistant
Copy link
Copy Markdown

cla-assistant Bot commented Apr 16, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@SAY-5
Copy link
Copy Markdown
Author

SAY-5 commented Apr 28, 2026

Closing — typo-only PR. Multiple maintainers across the OSS ecosystem have flagged my recent typo-sweep PRs as AI-generated spam (notably hashicorp/nomad#27855, hashicorp/hcl#794, argo-cd reviewers). I should have caught this pattern sooner. Apologies for the noise.

@SAY-5 SAY-5 closed this Apr 28, 2026
@bric-stripe
Copy link
Copy Markdown
Collaborator

I should have caught this pattern sooner. Apologies for the noise.

np, thanks for following up. fwiw we fixed the typo in our internal repo and it'll get updated when we publish the next release.

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.

2 participants