run dependabot one day a week#58
Conversation
The old setup checked for updates every day and auto-merged them the same day. That didn't work well for for fast-moving dependencies because the same package could be bumped on consecutive days as new eligible releases kept appearing. This moves the repo to a weekly batch window instead. Dependabot now runs four times on the day assigned for this repo, spaced two hours apart, and [mrj](https://github.com/dhth/mrj) is expected to run in the interleaved hours. That keeps follow-up updates inside the same maintenance window, frees the open PR slot between runs, and reduces the day-to-day drip of small dependency PRs. EOF && git push -u origin run-dependabot-once-a-week && gh pr create --title "run dependabot one day a week" --body-file - <<'EOF' The old setup checked for updates every day and auto-merged them the same day. That didn't work well for for fast-moving dependencies because the same package could be bumped on consecutive days as new eligible releases kept appearing. This moves the repo to a weekly batch window instead. Dependabot now runs four times on the day assigned for this repo, spaced two hours apart, and [mrj](https://github.com/dhth/mrj) is expected to run in the interleaved hours. That keeps follow-up updates inside the same maintenance window, frees the open PR slot between runs, and reduces the day-to-day drip of small dependency PRs.
|
Warning Review limit reached
More reviews will be available in 20 minutes and 20 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
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
The old setup checked for updates every day and auto-merged them the
same day. That didn't work well for for fast-moving dependencies because
the same package could be bumped on consecutive days as new eligible
releases kept appearing.
This moves the repo to a weekly batch window instead. Dependabot now
runs four times on the day assigned for this repo, spaced two hours
apart, and mrj is expected to run in the
interleaved hours. That keeps follow-up updates inside the same
maintenance window, frees the open PR slot between runs, and reduces the
day-to-day drip of small dependency PRs.