fix: handle beginner label in triage workflow

[NssGourav]

Description:

Fix the triage review workflow condition for beginner labeled PRs.

• Remove the redundant ${{ }} wrapper from the job-level if condition
• Add support for the skill: beginner label in the triage review workflow
• Preserve the existing Good First Issue and beginner label checks
• Format the workflow condition and GitHub script block for readability

Related issue(s):

Fixes #2227

Notes for reviewer:

This is a CI workflow only change. GitHub Actions evaluates job-level if: conditions as expressions by default, so removing the wrapper avoids YAML parsing issues with labels containing a colon, such as skill: beginner.

Validated locally:

• Parsed .github/workflows/request-triage-review.yml with Python YAML loading
• Ran actionlint with the repository’s custom self-hosted runner label warning ignored

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 56a3551e-99b9-41b9-9001-bcc1ed1d007f

📥 Commits

Reviewing files that changed from the base of the PR and between 6ff9e83 and 065b62b.

📒 Files selected for processing (1)

• .github/workflows/request-triage-review.yml

---

Walkthrough

Reformats the request-triage job if condition into a multiline OR expression and reindents the inline actions/github-script JavaScript so listComments and createComment consistently pass owner, repo, and issue_number; triage comment creation remains gated on absence of <!-- triage -->.

Changes

GitHub Actions Workflow Fix

Layer / File(s)	Summary
Job Condition Expression .github/workflows/request-triage-review.yml (range_f2c570beace7)	Reformatted jobs.request-triage.if from a single-line expression to a multiline if: > OR chain keeping the same three contains(...) label checks.
Embedded Script Formatting .github/workflows/request-triage-review.yml (range_6e29351e8dde)	Reindented inline JavaScript so github.rest.issues.listComments and the conditional github.rest.issues.createComment consistently pass owner, repo, and issue_number from context; preserved <!-- triage --> existence gating.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing the triage workflow to handle the beginner label by removing the ${{ }} wrapper and adding skill: beginner support.
Description check	✅ Passed	The description clearly explains the fix, lists all changes made, references the linked issue #2227, and includes validation details and a checklist.
Linked Issues check	✅ Passed	The PR successfully addresses issue #2227 by removing the ${{ }} wrapper from the if condition and adding support for the 'skill: beginner' label alongside existing label checks.
Out of Scope Changes check	✅ Passed	All changes are directly related to fixing the triage workflow and are scoped to the .github/workflows/request-triage-review.yml file only.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

📋 Issue Planner

Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).

View plan for ticket: #2227

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[ManmathX]

LGTM - Great work on identifying and fixing this, @NssGourav! 🎉

The root cause analysis is spot-on — the ${{ }} wrapper inside the if: condition causes YAML to misinterpret the colon in 'skill: beginner' as a key-value separator. Since GitHub Actions automatically evaluates if: conditions as expressions, removing the wrapper is the cleanest fix.

One small suggestion for improvement:
The indentation of the JavaScript block inside actions/github-script (lines 31–43) is a bit inconsistent — some lines use different levels of indentation. If you'd like to clean that up in the same PR, it would make the file easier to maintain going forward. Totally optional though, the core fix is what matters here.

Thanks for the contribution! 🙌

[NssGourav]

Thanks @ManmathX ,addressed the feedback cleaned the branch history and normalizing github script indentation.

[aceppaluni]

@NssGourav

This is looking good. Are you able to share a link to your test?

[NssGourav]

@NssGourav

This is looking good. Are you able to share a link to your test?

Sure, I added the test evidence here:
NssGourav#2

It includes the successful pre commit run from before the rebase and notes that the latest upstream workflow runs are awaiting maintainer approval after rebasing.

[aceppaluni]

@NssGourav This is great!

Please update your branch and then we can merge. Thank you!

[github-actions]

Hi, this is WorkflowBot.
Your pull request cannot be merged as it is not passing all our workflow checks.
Please click on each check to review the logs and resolve issues so all checks pass.
To help you:

• DCO signing guide
• Merge conflicts guide
• Rebase guide
• Testing guide
• Discord
• Community Calls
  Thank you for contributing!
  From the Hiero Python SDK Team

[aceppaluni]

@NssGourav Thank you so much!