docs: Add PR title check workflow

[hupling]

Pull Request

Changes

• check pr title

Reference

Relates to #314

Testing

URL to pull request or branch for testing your changes in sps-repo : dieser pr

Checklist

Note: If some checklist items are not relevant for your PR, just remove them.

General

• Met all acceptance criteria of the issue
• Added meaningful PR title and list of changes in the description
• Documented changes in documentation files (docs/action.md, docs/workflows.md and/or docs/deployment.md)
• Tested changes with sample project https://github.com/it-at-m/sps

Code

• Wrote code and comments in English
• Coming soon: Added unit tests

Summary by CodeRabbit

• Chores
  • Added automated pull request title validation.
  • Titles must begin with feat:, fix:, or docs:, with an optional scope.

[coderabbitai]

Warning

Review limit reached

@hupling, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 77e75b80-3c74-4049-8c25-38fba606b6eb

📥 Commits

Reviewing files that changed from the base of the PR and between a2fe20e and 124d90f.

📒 Files selected for processing (1)

• .github/workflows/pr-title-check.yml

📝 Walkthrough

Walkthrough

Adds a GitHub Actions workflow that validates pull request titles on selected lifecycle events. Titles must begin with feat:, fix:, or docs:, optionally followed by a scope, or the check fails.

Changes

PR title validation

Layer / File(s)	Summary
Title check workflow .github/workflows/pr-title-check.yml	Runs on selected pull request events, validates the title prefix and optional scope with a shell regex, and reports success or failure.

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 is concise and accurately summarizes the added PR title check workflow.
Description check	✅ Passed	The description follows the template and includes changes, reference, testing, and checklist sections; the testing link text should be a real URL.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 314-check-pr-title

---

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

[ejcsid]

Mir scheint, dass die Action die da verwendet wird, nicht gut gepflegt ist. Und ich bin mir auch unsicher, ob es wirklich eine externe Action dafür braucht. Eigentlich ist es doch nur eine Regex die auf den Titel des PR ausgeführt wird.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/pr-title-check.yml:
- Around line 3-5: Add a concurrency group to the pull request title-check
workflow using the pull request identifier, and enable cancellation of
in-progress runs. Ensure newer opened, edited, synchronize, or reopened events
cancel superseded runs for the same pull request while retaining the existing
trigger types.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 183b207c-326a-4c3a-86e1-e8a4e4b118dc

📥 Commits

Reviewing files that changed from the base of the PR and between 4ed8f90 and a2fe20e.

📒 Files selected for processing (1)

• .github/workflows/pr-title-check.yml