Loading
Clean up merge schedules with invalid merge_after
What does this MR do and why?
Merge schedules with a merge_after: nil are invalid and are currently a no-op. In the backend MR to introduce merge_before we introduce a validation that merge_after must be present. This MR creates migrations to clean up the invalid entries and adds a not null constraint to prevent those records on the database layer.
| Changes | MR |
|---|---|
| Most backend changes | !258024 (merged) |
| Cleanup migrations | |
| Frontend & Controller | !258025 (merged) |
References
Split of from !258024 (comment 4007735800)
Related to Allow end time in merge schedule (#630505 - closed)
Screenshots or screen recordings
No UI changes
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.