feat(mergify): update rule to require conversation resolution#4142
feat(mergify): update rule to require conversation resolution#4142mergify[bot] merged 2 commits intomasterfrom
Conversation
WalkthroughThe Changes
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.mergify.yml (1)
35-35: Update rule name to reflect queue behavior
Renamed from "Automatic merge" to "Automatic merge queue" for clarity. Verify that any documentation or tooling references are updated to match this new name.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
.mergify.yml(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: lint_test_build
- GitHub Check: Summary
🔇 Additional comments (2)
.mergify.yml (2)
14-14: Formatting-only update
Blank line adjustments for readability; no functional impact.Also applies to: 33-33
21-21: Enforce resolved review threads before merge
This new queue condition (#review-threads-unresolved=0) ensures all PR conversations are marked as resolved prior to merging, aligning with the internal guidance.
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks. You may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
Internal guidance: all conversations on pull requests must be marked as resolved before merging
Summary by CodeRabbit