BE-659 | Update required labels

[deividaspetraitis]

Pipeline: require backport to v28.x

Summary by CodeRabbit

• Chores
  • Updated workflow configuration for required labels to reflect new versioning and label requirements.

[coderabbitai]

Walkthrough

The pull request updates the workflow configuration in the .github/workflows/required-labels.yml file. It modifies the target branch from "v26.x" to "v27.x" and changes the required label from "A:backport/v27.x" to "A:backport/v28.x". These adjustments impact the triggering conditions of the workflow and specify the necessary labels for successful execution.

Changes

File	Change Summary
.github/workflows/required-labels.yml	Updated branch from "v26.x" to "v27.x" and label from "A:backport/v27.x" to "A:backport/v28.x".

Possibly related PRs

• chore: add required labels check for backporting #543: The changes in this PR also involve updates to the .github/workflows/required-labels.yml file, specifically modifying the required label for backporting from "A:backport/v26.x" to "A:backport/v27.x", which is directly related to the changes made in the main PR.

Suggested reviewers

• cryptomatictrader
• PaddyMc
• crnbarr93
• p0mvn

🐰 In the garden, we hop and play,
New labels bloom, brightening the day.
From v26, we leap to v27,
With backports ready, let’s count to ten!
A workflow fresh, a joyful cheer,
Hopping along, we have nothing to fear! 🌼

---

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 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: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 16e9207 and 04215a6.

📒 Files selected for processing (1)

• .github/workflows/required-labels.yml (2 hunks)

🔇 Additional comments (1)

.github/workflows/required-labels.yml (1)

29-29: Label requirement update looks good

The label requirement "A:backport/v28.x" correctly aligns with the PR objectives for v28.x backporting.

[coderabbitai]

⚠️ Potential issue

Branch targeting appears inconsistent with PR objectives

The workflow is configured to trigger on branch "v27.x", but the PR objectives mention the need for a backport to v28.x. Should this be targeting "v28.x" instead?

- branches:
-   - "v27.x"
+ branches:
+   - "v28.x"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- "v27.x"
	- "v28.x"

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud