Skip to content

ci: fix some typos - #27

Closed
JamBalaya56562 wants to merge 1 commit into
canaryfrom
ci-typos
Closed

JamBalaya56562 wants to merge 1 commit into
canaryfrom
ci-typos

Conversation

@JamBalaya56562

@JamBalaya56562 JamBalaya56562 commented Aug 11, 2025 •

Copy link
Copy Markdown
Owner

Summary by Sourcery

Correct spelling mistakes across CI workflow configs, GitHub Action source code, error messages, comments, and log messages.

Enhancements:

  • Fix spelling of "positive" in maxConcurrentStreams error messages
  • Correct typos in comments and log outputs (e.g., "Flakiness", "comparisons", "Construct") in the integration-stat action
  • Fix typo in workflow YAML descriptions (e.g., "Packages", "identifier")

CI:

  • Fix typos in build_and_deploy and integration_tests_reusable workflow files

@sourcery-ai

sourcery-ai Bot commented Aug 11, 2025 •

Copy link
Copy Markdown

Reviewer's Guide

This PR corrects spelling mistakes across the CI action code and workflow configurations by updating error messages, console logs, code comments, and workflow descriptions to their proper forms.

File-Level Changes

Change Details Files
Correct spelling of 'positive' in error messages
  • Replaced 'possitive' with 'positive' in maxConcurrentStreams error message (two occurrences)
.github/actions/next-integration-stat/dist/index.js
Update console.log spelling from 'Flakyness' to 'Flakiness'
  • Adjusted console.log output in dist build
  • Adjusted console.log output in TypeScript source
.github/actions/next-integration-stat/dist/index.js
.github/actions/next-integration-stat/src/index.ts
Fix typos in code comments
  • Corrected 'comparisons' spelling in comments
  • Corrected 'Construct' spelling in comments
.github/actions/next-integration-stat/dist/index.js
.github/actions/next-integration-stat/src/index.ts
Update workflow descriptions
  • Fixed 'Pacakges' to 'Packages' in build_and_deploy workflow
  • Fixed 'identifer' to 'identifier' in integration tests workflow
.github/workflows/build_and_deploy.yml
.github/workflows/integration_tests_reusable.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@JamBalaya56562
JamBalaya56562 force-pushed the ci-typos branch 3 times, most recently from 632035a to f8fbe44 Compare August 11, 2025 06:51
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.

1 participant