feat: add conventional PR title workflow#39
Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 46 minutes and 1 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Branch preview🔗 https://add-conventional-pr-title.chinmina.pages.dev (direct commit link) |
8a11a9f to
9d5402a
Compare
9d5402a to
c4df6f3
Compare
Purpose
Enforces Conventional Commits formatting on PR titles across the repo.
Consistent PR titles keep the commit history machine-readable when using a
squash-merge workflow, making changelog generation reliable and the project
history easy to navigate.
The check is implemented via a shared reusable workflow in
chinmina/.github,so the enforcement rule and its underlying action are maintained in one place
across the org.
Context
amannn/action-semantic-pull-requestv6.1.1 pinned by SHA