Missing gitlab_group.allow_merge_on_skipped_pipeline options
I'd really like to be able to manage this option on a Group level instead of project level. With our implemented permission model this can now be disabled by Users, we want to prevent that. This would help us tremendously on auditability.
- Subscription: GitLab Ultimate
- Product: gitlab.com
- Why interested?
- We want this setting enforced in a way users can't work around this. We want this a part of our audit trail
- Problem they are trying to solve:
- Ensuring that each code evolution is checked and controlled by pipeline tasks
- Current solution for this problem: Apply this setup at the project level (several hundreds of projects...) or manual on group level (100+ groups)
- Impact to the customer of not having this: Time consuming, less efficiency and more manual work on audit trails.
Edited by 🤖 GitLab Bot 🤖