chore(ci): forward port setting in the mergify.yml

[kobakaku]

Closes #3917

Overview

It modifies mergify.yml.
By adding the forwardport:main tag to the v1.x or v2.x branch, it can forward-port it to the main branch.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes introduce two new rules to the .github/mergify.yml configuration file to facilitate forward-porting of patches to the main branch from the v1.x and v2.x branches. These rules are triggered when a pull request targeting either of these branches is labeled with forwardport:main, allowing for streamlined version control management.

Changes

File	Change Summary
.github/mergify.yml	Added two new rules for forward-porting patches: one for v1.x and another for v2.x, both triggered by the forwardport:main label.

Assessment against linked issues

Objective	Addressed	Explanation
Configure mergify to support forward-porting to main (#3917)	✅

Possibly related PRs

• ci: enable backporting to v2.x #3658: This PR adds a new rule to backport patches to the v2.x branch, which is directly related to the new rule for v2.x introduced in the main PR.

---

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:

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

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.github/mergify.yml (1)

18-33: Consider adding documentation for new labels

The new rules successfully implement the forward-porting functionality as requested. To ensure proper usage, consider adding documentation or guidelines on how and when to apply the forwardport:main label to pull requests.

This documentation could be added to the repository's contributing guidelines or README file to help developers understand and utilize this new feature effectively.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 66e5511 and 5c2bc00.

📒 Files selected for processing (1)

• .github/mergify.yml (1 hunks)

🔇 Additional comments (2)

.github/mergify.yml (2)

18-25: LGTM: New rule for forward-porting from v1.x to main

This new rule correctly implements the forward-porting functionality from the v1.x branch to the main branch. It uses the appropriate conditions and actions to achieve the desired behavior.

This addition aligns with the PR objectives and addresses the need outlined in issue #3917.

---

26-33: LGTM: Consistent rule for forward-porting from v2.x to main

This rule mirrors the structure of the v1.x rule, providing consistent behavior for forward-porting from the v2.x branch to the main branch. The consistency between these rules is commendable.

This addition completes the implementation of the forward-porting functionality as requested in the PR objectives and issue #3917.

[rootulp]

Thanks! I just created the label forwardport:main so this LGTM. We can test after it merges.