chore: Updated coderabbit file for tone

[sagar-qa007]

Description

Tip

Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content, marketing, and DevRel team).

Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

Warning

If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation

/ok-to-test tags="@tag.IDE"

🔍 Cypress test results

Caution

🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/11384558809
Commit: b968db6
Cypress dashboard.
Tags: @tag.IDE
Spec:
The following are new failures, please fix them before merging the PR:

1. cypress/e2e/Regression/ClientSide/IDE/Focus_retentions_inputs_spec.js

List of identified flaky tests.

---

Thu, 17 Oct 2024 12:33:36 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

• Yes
• No

Summary by CodeRabbit

• Documentation
  • Updated tone instructions for code reviewers to clarify their role and expectations.
  • Added guidance on providing elaboration only upon request.

[coderabbitai]

Walkthrough

The changes involve updates to the .coderabbit.yaml configuration file, specifically within the tone_instructions section. The modifications clarify the role of the code reviewer, enhancing the description of expertise and refining the conditions under which elaboration is provided. The overall structure and other sections of the configuration remain unchanged.

Changes

File	Change Summary
.coderabbit.yaml	Updated tone_instructions to clarify the role of the code reviewer and refine elaboration conditions.

Suggested labels

skip-changelog

🌟 In the land of code, where reviews take flight,
An expert now shines, guiding through the night.
With clarity and precision, advice flows like streams,
Elaboration awaits, just ask for your dreams!
So here’s to the changes, brightening our way,
In the world of code, let’s code and play! 🎉

---

🪧 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.

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.coderabbit.yaml (1)

4-4: Remove trailing spaces for cleaner formatting.

There are trailing spaces at the end of line 4. While this doesn't affect functionality, removing them will improve code cleanliness and consistency.

Here's the suggested change:

-tone_instructions: 'You are an expert code reviewer in Java, TypeScript, JavaScript, and NodeJS. You work in an enterprise software developer team, providing concise and clear code review advice.You only elaborate or provide detailed explanations when requested.' 
+tone_instructions: 'You are an expert code reviewer in Java, TypeScript, JavaScript, and NodeJS. You work in an enterprise software developer team, providing concise and clear code review advice.You only elaborate or provide detailed explanations when requested.'

🧰 Tools

🪛 yamllint

[error] 4-4: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6a6ee9a and b968db6.

📒 Files selected for processing (1)

• .coderabbit.yaml (1 hunks)

🧰 Additional context used

🪛 yamllint

.coderabbit.yaml

[error] 4-4: trailing spaces

(trailing-spaces)

🔇 Additional comments (1)

.coderabbit.yaml (1)

4-4: LGTM! Improved clarity in tone instructions.

The updates to the tone_instructions field enhance the clarity and specificity of the AI reviewer's role. The changes accurately reflect best practices for code review, emphasizing conciseness and clarity while allowing for detailed explanations when necessary.

🧰 Tools

🪛 yamllint

[error] 4-4: trailing spaces

(trailing-spaces)