3 ms·
Before folks panic, this is not about requiring test results to pass to merge in a repo, but rather requiring a particular CI job/config to be in all repos on t
by the_weary_gamer 4y ago
Before folks panic, this is not about requiring test results to pass to merge in a repo, but rather requiring a particular CI job/config to be in all repos on the server.
It's questionable that they are moving this up a tier, but this feature really does seem like it makes the most sense as a compliance feature and all compliance features are 'Ultimate' already. Any other usage seems like it could be replaced by adding an 'include' directive to the relevant jobs.
- xenomachina 4y agoApproval rules are also arguably a "compliance feature". If they moved those up to Ultimate, I think they'd be making Premium useless for many teams.
- bradwood 4y agoI don't think this is a biggie. It could probably be worked around with a CODEOWNERS over .gitlab-ci.yml.