Rename sonarcloud.yml to sonar-cloud.yml

[guibranco]

Resolves #ISSUE_NUMBER

---

Before the change?

After the change?

Pull request checklist

• [ ] Tests for the changes have been added (for bug fixes/features)
• [ ] Docs have been reviewed and added/updated if needed (for bug fixes/features)

Does this introduce a breaking change?

• [ ] Yes
• [ ] No

---

Description by Korbit AI

What change is being made?

Rename sonarcloud.yml to sonar-cloud.yml.

Why are these changes being made?

This change standardizes the naming convention for workflow files, improving readability and consistency across the project.

[semanticdiff-com[bot]]

Review changes with SemanticDiff.

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. It looks like you've already reached the 5 review limit on our Basic Plan for the week. If you still want a review, feel free to upgrade your subscription in the Web App and then reopen the PR

[korbit-ai[bot]]

My review is in progress :book: - I will have feedback for you in a few minutes!

[pr-code-reviewer[bot]]

:wave: Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo. Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[codara-ai-code-review[bot]]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. .github/workflows/sonar-cloud.yml: Renaming a file from sonarcloud.yml to sonar-cloud.yml can lead to issues, especially in case-sensitive environments or scripts that may still refer to the old filename.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. .github/workflows/sonar-cloud.yml: When renaming files, ensure to update any references to the old file name in scripts, configurations, or workflows to avoid any potential breakages.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Review was skipped as selected files did not have any reviewable changes.

Files selected but had no reviewable changes (1)

* .github/workflows/sonar-cloud.yml

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[gooroo-dev[bot]]

Please double check the following review of the pull request:

Issues counts

🐞Mistake	🤪Typo	🚨Security	🚀Performance	💪Best Practices	📖Readability	❓Others
0	0	0	0	0	0	0

Changes in the diff

• 🛠️ Renamed sonarcloud.yml to sonar-cloud.yml.

Identified Issues

No issues found in the incoming changes.

Explanation

The proposed change is a simple file rename from sonarcloud.yml to sonar-cloud.yml. This change does not introduce any code modifications or new features, nor does it remove any existing functionality. There are no mistakes, typos, security issues, performance concerns, best practice violations, or readability issues identified in this diff. Therefore, no further action is required.

Missing Tests

As the change only involves renaming a file and does not alter any code logic or functionality, no new tests are necessary.

Summon me to re-review when updated! Yours, Gooroo.dev Please reply or add a reaction to this review.

[instapr[bot]]

### Feedback
- ✅ Tests and docs checklist items are completed.
- ✅ No breaking change introduced.
- ℹ️ Consider updating the "Before the change" and "After the change" sections with brief descriptions for clarity.

[codeclimate[bot]]

Code Climate has analyzed commit 18ca628c and detected 0 issues on this pull request.

View more on Code Climate.

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

6:08PM INF scanning for exposed secrets...
6:08PM INF 46 commits scanned.
6:08PM INF scan completed in 66.3ms
6:08PM INF no leaks found

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud