Repository navigation
Open
0 / 10 of 1 issue completedOpen
0 / 10 of 1 issue completed
Copy link
Labels
epicLarge unit of work, consisting of multiple tasksLarge unit of work, consisting of multiple taskshelp wantedReady to be picked up by anyone in the communityReady to be picked up by anyone in the communitymaintenanceRoutine upkeep necessary for the health of the platformRoutine upkeep necessary for the health of the platform
Description
Problem
40+ Open edX repos maintain their own near-duplicate renovate.json, and they've drifted over time — same intent, slightly different shapes. There's no single place to update org-wide policy (automerge rules, schedules, grouping, vulnerability alerts). Additional repos likely have no Renovate config at all and should be brought into the same scheme.
Two distinct patterns exist today:
- Frontend (~27 repos):
config:base, automerge@edx/@openedxminor+patch,rebaseStalePrs, oftenpatch.automerge: true. Some add weekly schedules,eslintgrouping, orsemanticCommits. - Backend (~13 repos):
config:base, broader automerge (minor,patch,pin,digest). A handful add schedules,prConcurrentLimit, or reviewer teams.
Phase 1 — Discovery
Content moved to sub-task
Phase 2 — Implementation
- Create the host repo / presets per Phase 1 decisions.
- Migrate the POC repos (1–2 FE, 1–2 BE) and let them bake long enough to see at least one real Renovate cycle. Adjust presets based on what we learn.
- Roll out to the remaining repos. Likely tracked as per-repo follow-up issues filed off this epic.
- Document the presets, override pattern, and how to onboard a new repo.
Out of scope (for this epic)
- Changing org-wide automerge / scheduling policy. This epic preserves current behavior; policy changes go in follow-ups against the central repo once it exists.
References
- Renovate shared config presets: https://docs.renovatebot.com/config-presets/
- Existing FE example:
openedx/frontend-platform/renovate.json - Existing BE example:
openedx/credentials/renovate.json
Metadata
Metadata
Assignees
Labels
epicLarge unit of work, consisting of multiple tasksLarge unit of work, consisting of multiple taskshelp wantedReady to be picked up by anyone in the communityReady to be picked up by anyone in the communitymaintenanceRoutine upkeep necessary for the health of the platformRoutine upkeep necessary for the health of the platform
Type
Projects
- StatusShow more project fields📋 Backlog
Activity