ci: trigger checks on release-please branches

[FBumann]

Summary

• Add release-please--** to push triggers in ci.yaml so CI runs on release-please branches
• Add push trigger on release-please--** to pr-title.yaml with a no-op step (since bot PRs don't trigger pull_request events)

This unblocks release-please PRs that hang waiting for required status checks.

Test plan

• Verify release-please PR gets CI checks after merge

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@FBumann has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 17 minutes and 23 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.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 96f5c938-c735-45b4-8b55-257e7710ad43

📥 Commits

Reviewing files that changed from the base of the PR and between d9b0b8f and c3aa24d.

📒 Files selected for processing (2)

• .github/workflows/ci.yaml
• .github/workflows/pr-title.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/release-please-checks

---

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