chore: apply Prettier auto-formatting to codebase

[aaronsteers]

Format the codebase using Prettier to ensure consistent styling and improve readability.

Summary by CodeRabbit

• New Features

  • Enhanced workflow for connector tests to improve handling of changes and job execution conditions.
  • Introduced a condition in the slash command dispatch workflow to restrict execution to pull requests only.

• Bug Fixes

  • Improved clarity and organization of various GitHub Actions workflows without altering their core functionality.

• Documentation

  • Updated migration guide for CDK to reflect significant changes in version 6.x.x and provide detailed migration instructions.
  • Enhanced Sphinx documentation with instructions for integrating new packages and modules.

• Chores

  • Consistent formatting updates across multiple workflow files for improved readability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes primarily involve formatting adjustments across multiple GitHub workflow files and configuration settings. Key modifications include changing string literals from single quotes to double quotes, restructuring job steps for clarity, and ensuring consistent indentation throughout YAML files. Additionally, enhancements to the handling of pull requests and job execution conditions were implemented in specific workflows. Overall, these updates focus on improving readability and organization without altering the core functionality of the workflows.

Changes

File Path	Change Summary
.github/release-drafter.yml	Changed single quotes to double quotes for string literals in various templates and labels.
.github/workflows/autofix-command.yml	Updated string literals to double quotes; reorganized job steps for clarity.
.github/workflows/connector-tests.yml	Defined concurrency for job runs; improved handling of pull request events and job conditions.
.github/workflows/pdoc_preview.yml	Reformatted indentation for consistent YAML structure.
.github/workflows/pdoc_publish.yml	Adjusted formatting for consistency; no changes to logic.
.github/workflows/poetry-lock-command.yml	Updated string literals to double quotes; streamlined job configuration.
.github/workflows/pypi_publish.yml	Reformatted steps for consistent indentation; functionality unchanged.
.github/workflows/python_lint.yml	Adjusted indentation for clarity; no changes to job logic.
.github/workflows/python_pytest.yml	Reformatted YAML indentation; maintained original functionality.
.github/workflows/slash_command_dispatch.yml	Added condition to restrict job execution to pull requests; other steps largely unchanged.
.github/workflows/test-command.yml	Reformatted job steps for clarity; maintained original logic.
cdk-migrations.md	Updated documentation for CDK changes, including method signature modifications and new components.
sphinx-docs.md	Enhanced documentation for adding new packages to Sphinx, including detailed integration steps.

Possibly related PRs

• CI: Add GitHub workflows, including testing, linting, release drafting, and documentation generation #2: The changes in the .github/release-drafter.yml file in both the main PR and this retrieved PR involve modifications to the same configuration file, specifically related to the formatting of string literals and the structure of the release drafter configuration.

Suggested labels

ci

Poem

🐰 In the garden where workflows bloom,
A rabbit hops, dispelling gloom.
With double quotes and tidy lines,
Our YAML sings, in perfect signs.
From tests to docs, all neatly set,
A clearer path, we won't forget! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.