-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Repository - Branch List
-
None
-
1
Branch restrictions now include a Pipelines write access setting. It lets admins choose which source branches can run pipelines that push back to a restricted branch.
At the moment, the setting only accepts exact branch names. Many teams create release, hotfix or similar branches regularly with a common naming convention (for example release/1.4, release/1.5). Those teams want pipelines on any of these branches to push back to a protected branch such as main, for example to update version numbers, changelogs or generated files.
Because patterns aren't supported, admins either have to update the branch restriction every time a new branch is created, or keep using access tokens or other credentials to push to the restricted branch. That keeps the broader credentials the feature is meant to replace.