feat: add PR title validation workflow

[harshtandiya]

• Introduced a GitHub Actions workflow to validate pull request titles against conventional commit standards.
• The workflow triggers on PR events (opened, reopened, synchronized, edited) and provides feedback on title formatting.
• Includes documentation for allowed title formats and examples to guide contributors in writing appropriate titles.

Summary by CodeRabbit

• Chores
  • Added automated PR title validation that runs on pull request events, checks title format against conventional-commit-like rules, prints actionable guidance when a title is invalid, and fails the check to enforce compliant PR titles.

[coderabbitai]

Warning

Rate limit exceeded

@harshtandiya has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 49 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

Adds a new GitHub Actions workflow that validates pull request titles on PR events using amannn/action-semantic-pull-request (v6.1.1). If validation fails the job prints structured guidance and exits with a non‑zero status.

Changes

Cohort / File(s)	Summary
PR Title Validation Workflow ​.github/workflows/pr-title-check.yml	Adds a workflow triggered on PR opened/reopened/synchronize/edited. Runs on ubuntu-latest, grants pull-requests write permission, executes amannn/action-semantic-pull-request@v6.1.1 (wip enabled, scope not required) and, on failure, prints detailed guidance and exits with code 1.

Sequence Diagram(s)

sequenceDiagram
    participant User as User (opens PR)
    participant GitHub as GitHub Actions
    participant Runner as Actions Runner
    participant Action as Semantic PR Action

    User->>GitHub: Open/Reopen/Synchronize/Edit PR
    GitHub->>Runner: Trigger pr-title-check workflow
    Runner->>Action: Run amannn/action-semantic-pull-request@v6.1.1
    Action-->>Runner: Validation result (pass/fail)
    alt pass
        Runner-->>GitHub: Job completes (success)
    else fail
        Runner->>Runner: Print failure documentation
        Runner-->>GitHub: Job fails (exit 1)
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped in to check each title bright,

With dots and scopes aligned just right,
If dullness creeps, I tap the bell,
A friendly note to make it well,
Hooray — neat PRs take flight! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The pull request title 'feat: add PR title validation workflow' directly and accurately summarizes the main change—adding a new GitHub Actions workflow for PR title validation.

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @.github/workflows/pr-title-check.yml:
- Line 16: The workflow uses an invalid runner label "ubuntu-slim" in the
runs-on setting; update the runs-on value in the CI workflow (the runs-on entry
in the YAML for the PR title check) to a valid GitHub-hosted runner such as
"ubuntu-latest" or a specific supported label like "ubuntu-24.04" to prevent
immediate workflow failure.
- Around line 29-32: The PR title is being interpolated directly into the shell
run block (echo "**Current title:** `${{ github.event.pull_request.title }}`"),
creating a command-injection risk; change the step to pass
github.event.pull_request.title into a safe environment variable (e.g., env:
PR_TITLE: ${{ github.event.pull_request.title }}) and then reference that
variable in the run script using a safe expansion/printing idiom (for example
echo "**Current title:** \"$PR_TITLE\"" or printf '%s\n' "$PR_TITLE") so
backticks or other shell metacharacters cannot be executed; update the run block
where the current title is printed to use PR_TITLE instead of direct
interpolation.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

ubuntu-slim is not a valid GitHub-hosted runner label.

This will cause the workflow to fail immediately. Use ubuntu-latest (or a specific version like ubuntu-24.04).

Proposed fix

-    runs-on: ubuntu-slim
+    runs-on: ubuntu-latest

📝 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

	runs-on: ubuntu-slim
	runs-on: ubuntu-latest

🤖 Prompt for AI Agents

In @.github/workflows/pr-title-check.yml at line 16, The workflow uses an
invalid runner label "ubuntu-slim" in the runs-on setting; update the runs-on
value in the CI workflow (the runs-on entry in the YAML for the PR title check)
to a valid GitHub-hosted runner such as "ubuntu-latest" or a specific supported
label like "ubuntu-24.04" to prevent immediate workflow failure.

[harshtandiya]

ubuntu-slim is a valid runner

[coderabbitai]

🧩 Analysis chain

🌐 Web query:

GitHub Actions ubuntu-slim runner 2026

💡 Result:

In 2026, ubuntu-slim is a GitHub-hosted runner label for a single-CPU Ubuntu environment intended for lightweight/short jobs (automation, issue ops), not heavyweight CI builds [1]. It runs in a container (not a full VM) and comes with a minimal preinstalled toolset [1].

Specs / limits (standard runners):

• 1 vCPU, 5 GB RAM, 14 GB SSD, x64 [1]
• Job timeout: 15 minutes [1]

How to use:

jobs:
  build:
    runs-on: ubuntu-slim

ubuntu-slim is listed as an Ubuntu Slim (preview) image in the actions/runner-images repo (the source of what’s installed on GitHub-hosted runner images) [2].

Sources: GitHub-hosted runners reference [1]; actions/runner-images README [2].

---

@harshtandiya, you're absolutely correct, and I apologize for the incorrect review comment.

ubuntu-slim is indeed a valid GitHub-hosted runner label introduced as a preview feature. It's a single-CPU Ubuntu environment designed specifically for lightweight automation tasks like PR title validation, with these characteristics:

• 1 vCPU, 5 GB RAM, 14 GB SSD
• 15-minute job timeout
• Runs in a container (not a full VM)
• Minimal preinstalled toolset

This runner is actually well-suited for your PR title validation workflow since it's a lightweight task that doesn't require extensive resources. Thank you for the correction!