Repository navigation
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Dependabot rebase workflow now triggers on a scheduled cron basis every 4 hours as a safety net, in addition to the existing push trigger on main. Inline comments explain the scheduled trigger rationale. The file was also cleaned up by removing extraneous content. ChangesWorkflow trigger configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
Pull request overview
Updates the repo’s Dependabot rebase/merge “thin caller stub” workflow to a newer reusable-workflow commit and adds a scheduled trigger to keep the Dependabot queue moving even when main is quiet.
Changes:
- Bump the referenced reusable workflow SHA for
dependabot-rebase-reusable.yml. - Add an
on.schedulecron trigger (every 4 hours) alongside the existingpush+workflow_dispatchtriggers.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| name: Dependabot update and merge | ||
|
|
||
| on: |
| pull-requests: write # call update-branch API on behind PRs and merge when ready | ||
| uses: petry-projects/.github/.github/workflows/dependabot-rebase-reusable.yml@b51e2edf830ea085be0277bcf3174c7b3ec8f958 # v1 | ||
| uses: petry-projects/.github/.github/workflows/dependabot-rebase-reusable.yml@02ce89bb84ba8fe7650f97522893cfdab25e060a # v1 |
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: 1272435b13fdb4acb2de927d76806ee7e2280ff9
Review mode: triage-approved (single reviewer)
Summary
Prompt-only changes to the org status report template that reduce output size by ~29K bytes. Three changes: (1) Open Issues grouped by repo subsection instead of flat table, dropping the repeated Repo column; (2) duplicate [#N](url) | [title](url) cells merged into single [#N — title](url) cells across Needs Human Review, Open Issues, and Open Discussions tables; (3) MAX_BYTES bumped from 60000 to 64000 (still 1536 bytes below GitHub's 65536 char limit). No data-shape changes.
Linked issue analysis
No closing issue linked, but the PR body clearly describes the problem: daily report #233 exceeded the 60000-byte truncation threshold, causing head -c to drop the start of the report (the @org-leads opener and first three sections). The changes directly address this by shrinking the rendered output.
Findings
No issues found.
- MAX_BYTES 64000: Safe — leaves 1536 bytes of headroom below GitHub's 65536-char issue body limit. Combined with the ~29K reduction in report size, truncation should rarely trigger.
- Prompt template changes: Clean restructuring. The per-repo subsection format for Open Issues and the single-link cell pattern are consistent across all three tables.
- No security concerns: No secrets, auth, eval, injection vectors, or CI security changes.
- Copilot's suppressed comment about UTF-8 truncation in
head -cis a pre-existing concern in the truncation step, not introduced by this PR.
CI status
All checks passed:
- Lint: ✓
- ShellCheck: ✓
- Agent Security Scan: ✓
- AgentShield: ✓
- CodeQL (actions): ✓
- SonarCloud: ✓ (0 new issues, 0 security hotspots)
- Dependency audit: ✓
Reviewed automatically by the PR-review agent (single-reviewer). Reply if you need a human review.
|
Auto-rebase failed — merge conflict — this branch has conflicts with Please resolve the conflicts and push: |
Pull request was closed
f22a9ef to
47c9309
Compare
|
Auto-rebase blocked — the base branch contains Please rebase this branch manually: |
|
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
@dev-lead - please fix this PR |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
|
Auto-rebase failed — merge conflict — this branch has conflicts with dev-lead will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention. To resolve manually instead: |
Superseded by automated re-review at
|
Superseded by automated re-review at 277c26e.
Review — fix requested (cycle 3/3)The automated review identified the following issues. Please address each one: Findings to fixAutomated review — NEEDS HUMAN REVIEWRisk: MEDIUM SummaryPR #154 is stuck: same HEAD SHA (277c26e) as the prior review cycle — the author has not pushed any changes. The branch has been conflicting with main since 2026-05-11 (23+ days, 15+ failed auto-rebase attempts) due to a permissions gap in the auto-rebase token for .github/workflows/ changes; manual rebase is required. Until the conflict is resolved and CI reruns, this PR cannot be approved. Findings
Reviewed by the PR-review cascade (triage: haiku 4.5 → deep: sonnet 4.6 + duck: o4-mini → audit: opus 4.7). Reply if you need a human review. Additional tasks
The review cascade will automatically re-review after new commits are pushed. |
|
Closing due to merge conflict — re-implementing from fresh main |
Pull request was closed



Summary
b51e2ed→02ce89b): The reusable workflow at02ce89bfixes a bug where a failedupdate-branchcall (due to missingworkflowspermission) caused the merge step to be skipped permanently; the fix falls through to a direct bypass merge instead.schedule: cron: '0 */4 * * *'trigger so the automerge chain doesn't stall when no pushes tomainoccur for days (e.g. quiet weekends).Changes
.github/workflows/dependabot-rebase.yml: updateduses:SHA and addedscheduletrigger to theon:block.Summary by CodeRabbit