CI: push trigger targets master, not main#31
Conversation
The push trigger listed branches: [main], but this repo's default branch is master - confirmed origin/HEAD points at master, and every prior push-based CI run only ever fired through the pull_request trigger. A direct push to master (including a merge commit) got no CI run at all.
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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. ✨ 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 |
1 participant
Fixes #16.
What
.github/workflows/ci.yml's push trigger listedbranches: [main]. This repo's default branch ismaster(confirmed viaorigin/HEAD→master), so the push trigger has never fired - every CI run so far only happened throughpull_request. A direct push tomaster, including a merge commit, gets no CI run at all.Fix
One line:
branches: [main]→branches: [master].