# Release post **Source Branch Pattern Exceptions** solve a critical workflow challenge for teams using GitFlow and similar branching strategies. This feature allows organizations to define branch-based exceptions in merge request approval policies, eliminating approval bottlenecks while maintaining security governance. ## Solving the GitFlow Challenge **The Problem**: When using GitFlow workflows, merging from `release/*` branches to `main` often leaves teams with few or no eligible approvers, since most contributors have already participated in the release branch development. This creates approval deadlocks that block critical releases. **The Solution**: Source branch pattern exceptions allow policies to automatically waive approval requirements based on source and target branch combinations. Teams can now configure policies that require strict approvals for feature-to-main merges while allowing streamlined release-to-main workflows. ## Key Capabilities **Pattern-Based Configuration**: Define flexible source branch patterns like `release/*`, `hotfix/*`, or `develop` that automatically bypass approval requirements when merging to specified target branches. This supports diverse branching strategies without compromising security for regular development workflows. **Seamless Integration**: Branch exceptions integrate directly into existing merge request approval policies through simple YAML configuration. No additional approval modals or manual intervention required—the exceptions apply automatically based on branch patterns, maintaining smooth release processes. This enhancement eliminates the need for complex workarounds while preserving the security benefits of approval policies for standard development workflows. # Related Issues This work is being tracked in https://gitlab.com/groups/gitlab-org/-/epics/14090, but is being released in multiple parts.