Update review rules

[dsikka]

• Require one review from a maintainer, unless the two-reviews label has been applied

[github-actions]

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8db4b28b-dbaf-40fa-9535-834103d09ce6

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

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[mergify]

Merge Protections

🟢 Merge protection satisfied — ready to merge.

Show 1 satisfied protection

🟢 📃 Configuration Change Requirements

Mergify configuration change

• check-success = Configuration changed

[gemini-code-assist]

Code Review

This pull request simplifies the PR review workflow by removing the automatic 'two-reviews' labeling for community PRs and introducing a new 'Require one maintainer review' rule in Mergify. Feedback suggests clarifying or updating the conditional logic (if: []) for this new rule to ensure it interacts correctly with the 'two-reviews' label as intended.

[kylesayrs]

Thanks