fix(dependency-review): only run on opened/reopened, not synchronize#2128
fix(dependency-review): only run on opened/reopened, not synchronize#2128
Conversation
Dependabot's synchronize events are almost always rebases that don't change the version being bumped. Running the full analysis on every synchronize produces duplicate, redundant comments on the PR (as seen on PR #2114 which received two identical Dependency Update Analysis comments). When dependabot finds a newer version it opens a new PR, so opened/reopened is sufficient coverage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Automatically handle the following tasks using AI:
Advanced controls
TroubleshootingThis control panel only adds or removes labels on the PR. |
|
|
Warning Rate limit exceeded
⌛ 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: Repository YAML (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Problem
The
dependency-review.ymlworkflow triggers on[opened, synchronize, reopened]. Thesynchronizeevent fires every time dependabot pushes to a PR branch — typically just a rebase to resolve merge conflicts. This caused PR #2114 to receive two identical Dependency Update Analysis comments (runs22830029727and22830956851).Root Cause
Dependabot almost never changes the version being bumped on an existing PR. When a newer version is available, it opens a new PR rather than updating the old one. So re-running the analysis on
synchronizeproduces redundant noise with no new information.Fix
Remove
synchronizefrom the trigger types — keep onlyopenedandreopened.