merge queue: embarking master (3edf47d) and #4174 together

[mergify]

❌ This pull request has failed checks. #4174 will be removed from the queue. ❌

Branch master (3edf47d) and #4174 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #4174.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue Automatic strict merge for merge:

• status-success = license/cla
• status-success = lint_test_build
• any of [🛡 GitHub branch protection]:
  • check-neutral = Summary
  • check-skipped = Summary
  • check-success = Summary
• any of [🛡 GitHub branch protection]:
  • check-neutral = lint_test_build
  • check-skipped = lint_test_build
  • check-success = lint_test_build
• any of [🛡 GitHub branch protection]:
  • check-neutral = license/cla
  • check-skipped = license/cla
  • check-success = license/cla
• any of [🛡 GitHub branch protection]:
  • check-neutral = lint_pull_request
  • check-skipped = lint_pull_request
  • check-success = lint_pull_request
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174

Required conditions to stay in the queue:

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• #approved-reviews-by >= 2
  • feat(metadata-view): Added Metadata V2 button #4174
• #changes-requested-reviews-by = 0
  • feat(metadata-view): Added Metadata V2 button #4174
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• #review-threads-unresolved = 0
  • feat(metadata-view): Added Metadata V2 button #4174
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• branch-protection-review-decision = APPROVED
  • feat(metadata-view): Added Metadata V2 button #4174
• branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
  • feat(metadata-view): Added Metadata V2 button #4174
• label != do-not-merge
  • feat(metadata-view): Added Metadata V2 button #4174
• label = ready-to-merge
  • feat(metadata-view): Added Metadata V2 button #4174
• status-success = license/cla
  • feat(metadata-view): Added Metadata V2 button #4174
• status-success = lint_pull_request
  • feat(metadata-view): Added Metadata V2 button #4174
• status-success = lint_test_build
  • feat(metadata-view): Added Metadata V2 button #4174
• title ~= ^(build|ci|chore|docs|feat|fix|perf|refactor|revert|style|test)(\([^)]+\))?:\s.+$
  • feat(metadata-view): Added Metadata V2 button #4174
• any of [🛡 GitHub branch protection]:
  • check-success = Summary
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-neutral = Summary
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-skipped = Summary
    • feat(metadata-view): Added Metadata V2 button #4174
• any of [🛡 GitHub branch protection]:
  • check-success = lint_test_build
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-neutral = lint_test_build
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-skipped = lint_test_build
    • feat(metadata-view): Added Metadata V2 button #4174
• any of [🛡 GitHub branch protection]:
  • check-success = license/cla
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-neutral = license/cla
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-skipped = license/cla
    • feat(metadata-view): Added Metadata V2 button #4174
• any of [🛡 GitHub branch protection]:
  • check-success = lint_pull_request
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-neutral = lint_pull_request
    • feat(metadata-view): Added Metadata V2 button #4174
  • check-skipped = lint_pull_request
    • feat(metadata-view): Added Metadata V2 button #4174

---
previous_failed_batches: []
pull_requests:
  - number: 4174
...

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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

---

🪧 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.
  • Explain this complex logic.
  • 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 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? Join our Discord community 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 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.

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