-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: django
-
None
-
None
-
Python Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Context
Django MongoDB Backend's docs describe what should happen when the upstream Django fork advances (per INTPYTHON-1019 and INTPYTHON-1025) but don't yet document the automation itself now that it's been implemented:
- INTPYTHON-1019 added a daily upstream-sync workflow that keeps each mongodb-X.Y.x fork branch current with upstream Django.
- INTPYTHON-1025 adds a reusable drivers-github-tools action to re-trigger django-mongodb-backend's CI after a fork-branch force-push.
Definition of done
- Describe the daily upstream-sync workflow: what triggers it, which branches it updates, and how conflicts/failures surface.
- Describe CI re-trigger mechanism: what event triggers a re-run (fork-branch force-push), which of the three ci_rerun kinds (evergreen/pr/ref) applies per branch, and where that mapping is configured (upstream-sync.yml's matrix).
- Link to the relevant workflow/action source for maintainers who need to change behavior.
Pitfalls
NA
- is blocked by
-
INTPYTHON-1025 Add drivers-github-tools action to re-trigger downstream CI after a fork-branch force-push
-
- Closed
-