docs: add guideline about timely response in PR reviews

[Adi-204]

Description
Add guideline about timely response in PR reviews. To keep the contribution process moving smoothly and avoid stale PRs.

Related issue(s)
Fixes #1619

Summary by CodeRabbit

• Documentation
  • Updated contribution guidelines to request contributors respond to maintainer reviews within 7 days. Pull requests may be closed if there is no response, but can be reopened or resubmitted later.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 825e566

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

"""

Walkthrough

A new guideline has been added to the contribution documentation, requesting contributors to respond to maintainer reviews on pull requests within 7 days. If no response is received, the pull request may be closed, with the option for contributors to reopen or submit a new PR later.

Changes

File(s)	Change Summary
CONTRIBUTING.md	Added a guideline about responding to maintainer reviews within 7 days and potential PR closure.

Assessment against linked issues

Objective	Addressed	Explanation
Add guideline for timely response to PR reviews and PR closure after 7 days (#1619)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes were found.
"""

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2181dfa and 78210e2.

📒 Files selected for processing (1)

• CONTRIBUTING.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• CONTRIBUTING.md

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: Acceptance tests for generated templates
• GitHub Check: Test generator as dependency with Node 18
• GitHub Check: Test generator as dependency with Node 20
• GitHub Check: Test NodeJS PR - windows-latest
• GitHub Check: Test NodeJS PR - ubuntu-latest
• GitHub Check: Test NodeJS PR - macos-13

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[sonarqubecloud]

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 SonarQube Cloud

[derberg]

/rtm