Enable ci_build_tags_limit by default
Ref: #339855 (closed)
What does this MR do?
This MR enables our ci_build_tags_limit
feature flag by default.
Why are we doing this?
In !68380 (merged) we introduced a limit to prevent pipeline creation for CI/CD build with more than 50 tags.
The feature got released on gitlab.com
since 2021-08-23
in #338929 (closed) without any performance degradation.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) - [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
- [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
- [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. - [-] This change is backwards compatible across updates, or this does not apply.