How to adopt a cascading merge request strategy with GitLab Flow
Aug 31, 2023Madou Coulibaly

Summary
This post introduces the 'ucascade' bot and details its deployment on Kubernetes, configuration via a JSON file, and integration with GitLab webhooks. It describes how to set up project access tokens and configure the bot to automatically create cascading merge requests across release branches when a change is merged into a primary branch. This automates a previously manual and time-consuming process for applying fixes to multiple stable branches.
More from the Issue and Merge Request Workflow Enhancements trail
- Agile planning gets a boost from new features in GitLab 18.10
- How we reduced MR review time with Value Stream Management
- Tutorial: Integrate GitLab Merge Request approvals with external systems
- How visualization improves the GitLab merge train experience
- Unveiling a new epic experience for improved Agile planning