yml files and build scripts changes in merge request protection

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

We have an option for Only allow merge requests to be merged if the build succeeds. The problem is that in branch it is possible to change yml file and build scripts, so your merge request will have succeeded build. The issue is that it will be good to centralize yml ( or even build scripts) changes.

Because now changing yml in branches decreases value of mentioned merge request verification build option.
Probably, we can notify in merge request that any yml was changed. May be it is something like lock file/folder feature, but more like "notifyOnMerge"* feature - file/folders. Merge requests that touches files/folder that are under "notifyOnMerge" will have additional notification that something important was changed.

Locking file in Gitlab EE possibly an option, but it is not about locking yml personal for some one, it is more about how to guarantee merge request policy. Also locking files not included in default license, you need to pay additional for this and this is not exactly what is needed.

Edited Aug 29, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading