You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: deduplicate Dependabot PRs in monorepo via group-by #43
Dependabot currently generates 2× PRs per bump for dependencies present in workspaces (apps/web, packages/type-testing). Root cause: the groups block in .github/dependabot.yml lacks group-by: dependency-name, so the same dep in N workspaces → N PRs.
Result: 20 open PRs, ~17 are root/workspace duplicates.
Solution
Add group-by: dependency-name to both groups (production-dependencies + development-dependencies) in .github/dependabot.yml — collapses PRs on the next weekly run
Enable auto-merge — Settings → General → "Allow auto-merge" + create .github/workflows/dependabot-auto-merge.yml to auto-merge minor/patch Dependabot PRs after CI passes (excluding majors)
Clean up the current stack — merge workspace PRs first, then close the duplicate root PRs
Acceptance Criteria
group-by: dependency-name added → next Dependabot run generates ≤ 10 PRs (one per dep)
20 open Dependabot PRs merged or closed
Auto-merge workflow active and functional
versioning-strategy for the published lib (packages/type-testing/) evaluated separately
Verification: CONFIRMED — .github/dependabot.yml has groups for both production-dependencies and development-dependencies but neither has group-by: dependency-name. Without it, Dependabot opens one PR per workspace for each dep bump — consistent with the 20 open Dependabot PRs currently in the repo. No auto-merge workflow exists. The learning doc at docs/internal/learnings/github/dependabot-pnpm-monorepo-2026.md validates the fix.
Next steps: This issue is ready to be picked up. The core fix is a one-line addition (group-by: dependency-name) to each group in .github/dependabot.yml. The auto-merge workflow and current PR cleanup are follow-on steps.
Related: #44 (staging branch) is blocked by this — once group-by lands and the staging branch exists, the same .github/dependabot.yml will need target-branch: staging.
Activity
martyy-code commentedon Jul 13, 2026
Triage complete
Verification: CONFIRMED —
.github/dependabot.ymlhasgroupsfor bothproduction-dependenciesanddevelopment-dependenciesbut neither hasgroup-by: dependency-name. Without it, Dependabot opens one PR per workspace for each dep bump — consistent with the 20 open Dependabot PRs currently in the repo. No auto-merge workflow exists. The learning doc atdocs/internal/learnings/github/dependabot-pnpm-monorepo-2026.mdvalidates the fix.Next steps: This issue is ready to be picked up. The core fix is a one-line addition (
group-by: dependency-name) to each group in.github/dependabot.yml. The auto-merge workflow and current PR cleanup are follow-on steps.Related: #44 (staging branch) is blocked by this — once
group-bylands and the staging branch exists, the same.github/dependabot.ymlwill needtarget-branch: staging.Triage by @martyy-code.