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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 55 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

Run ID: e655360d-d1aa-4a24-9610-1307a70f2464

📥 Commits

Reviewing files that changed from the base of the PR and between 798bbf1 and 72717d9.

📒 Files selected for processing (1)

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

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

[ejcsid]

wird die Action Slashgear/action-check-pr-title noch gepflegt. LCM seit Ende 2025 nicht erfolgt...

[hupling]

https://github.com/Slashgear/action-check-pr-title/releases/tag/action-check-pr-title-v6.0.0

also für mich 4. März 2026 aktuell. aber ich bin jetzt auch in die Bequemlichkeit gekommen, irgendwelche externen Actions zu nehmen.

Ich schaue, dann wie ich das selber sctipten kann