diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-15 03:10:54 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-02-15 03:10:54 +0000 |
| commit | 5c599896773669c8671fd14f79b96d9cd50ccab8 (patch) | |
| tree | 068ea44f71a34d897e47a0c834236d58ab028a67 /data | |
| parent | 03bea06527fd8cc8eb65af0b20b6019fc74721d9 (diff) | |
| download | gitlab-ce-5c599896773669c8671fd14f79b96d9cd50ccab8.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'data')
| -rw-r--r-- | data/deprecations/15-9-required-pipeline-configuration.yml | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/data/deprecations/15-9-required-pipeline-configuration.yml b/data/deprecations/15-9-required-pipeline-configuration.yml index 625d00cb07e..4aa3a83c51e 100644 --- a/data/deprecations/15-9-required-pipeline-configuration.yml +++ b/data/deprecations/15-9-required-pipeline-configuration.yml @@ -9,9 +9,10 @@ stage: Verify # (required) String value of the stage that the feature was created in. e.g., Growth issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/389467 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. - Required Pipeline Configuration will be removed in the 16.0 release. This impacts Self-Managed users on the Ultimate license. + Required Pipeline Configuration will be removed in the 16.0 release. This impacts self-managed users on the Ultimate license. - We recommend replacing this with an alternative [compliance solution](https://docs.gitlab.com/ee/user/group/compliance_frameworks.html#configure-a-compliance-pipeline) that is available now. We recommend this alternative solution because it provides greater flexibility, allowing required pipelines to be assigned to specific compliance framework labels. + We recommend replacing this with an alternative [compliance solution](https://docs.gitlab.com/ee/user/group/compliance_frameworks.html#compliance-pipelines) + that is available now. We recommend this alternative solution because it provides greater flexibility, allowing required pipelines to be assigned to specific compliance framework labels. # # OPTIONAL END OF SUPPORT FIELDS # |