Modify CodeRabbit trigger workflow to add the ready-to-test label

[tpantelis]

Summary by CodeRabbit

• Chores
  • Improved CI workflow automation to enhance testing process efficiency.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[submariner-bot]

🤖 Created branch: z_pr239/tpantelis/add_rtt-label

[coderabbitai]

Walkthrough

A new step is added to the GitHub Actions workflow that attaches a "ready-to-test" label to pull requests after auto-merge is enabled. The step includes error handling to prevent workflow failure if the label operation fails.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/coderabbit-trigger.yml	Adds a new workflow step with try/catch error handling to attach a "ready-to-test" label to the PR following auto-merge enablement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Add reusable workflow to trigger CodeRabbit review on bot PRs #231: Modifies the same GitHub Actions workflow to add GitHub API interaction steps for posting comments to trigger reviews.
• Modify CodeRabbit trigger workflow to Enable auto-merge #235: Modifies the same workflow file and implements the auto-merge step that precedes the new "ready-to-test" label attachment in this PR.

Suggested reviewers

• Oats87
• sridhargaddam
• skitt

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: modifying the CodeRabbit trigger workflow to add a 'ready-to-test' label, which directly matches the AI-generated summary.
Actionable Comments Resolved	✅ Passed	The pull request contains no actionable comments (TODO, FIXME, HACK) within the code. The workflow file includes only explanatory comments and the implementation is complete with proper error handling.

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd99511 and 9309a5d.

📒 Files selected for processing (1)

• .github/workflows/coderabbit-trigger.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Go

🔇 Additional comments (1)

.github/workflows/coderabbit-trigger.yml (1)

61-73: LGTM! Clean implementation with appropriate error handling.

The label addition step is well-implemented:

• Uses the correct GitHub API (github.rest.issues.addLabels)
• Properly scoped error handling that won't fail the workflow if the label doesn't exist
• Follows the established pattern from the auto-merge step above

The non-fatal error handling (logging vs. throwing) appropriately distinguishes between critical operations (auto-merge) and supplementary operations (label addition). The "ready-to-test" label is part of the bot's default configuration, and the graceful error handling correctly accounts for cases where the label may not exist in target repositories.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[submariner-bot]

🤖 Closed branches: [z_pr239/tpantelis/add_rtt-label]