ci: backport tags for release 4

[crnbarr93]

Motivation

Adds mergify handler for backport tags for release 4

Summary by CodeRabbit

• Chores
  • Enhanced automated backporting workflow by adding support for backporting changes to the release/4 branch
  • Improved release management configuration in GitHub merge rules

[coderabbitai]

Walkthrough

The pull request introduces a new backporting rule in the Mergify configuration file. This rule specifically targets the release/4 branch, allowing automatic backporting of changes from the main branch when a specific label is applied. The configuration extends the existing backporting strategy by adding support for another release branch, enhancing the project's release management workflow.

Changes

File	Change Summary
.github/mergify.yml	Added a new backporting rule for release/4 branch when labeled with backport/release/4

Poem

🐰 A rabbit's tale of branches neat,
Mergify's magic, now complete!
From main to release/4 we hop,
With labels guiding each code drop
Backporting made simple and bright 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6c29d1a and 9886db0.

📒 Files selected for processing (1)

• .github/mergify.yml (1 hunks)

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

• GitHub Check: Contract Tests (ubuntu-latest, integration-test)
• GitHub Check: Linting
• GitHub Check: Summary

🔇 Additional comments (1)

.github/mergify.yml (1)

24-31: LGTM! The backport rule is well-structured.

The new rule follows the established pattern and correctly configures backporting from main to release/4.

Let's verify the uniqueness of the backport labels to ensure there's no conflict:

✅ Verification successful

Backport labels are unique and follow consistent patterns

All backport labels are unique:

• backport/v1.1.x
• backport/release/3
• backport/release/4

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any conflicting or duplicate backport label definitions

# Search for all backport label definitions
echo "Checking for backport label definitions..."
rg -n 'label=backport/' .github/

Length of output: 294

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.