From 813bbbf499a15794301b5e06a9fcd72bef87c62c Mon Sep 17 00:00:00 2001 From: James Heimbuck Date: Thu, 16 Feb 2023 20:38:29 +0000 Subject: fix linting errors --- data/deprecations/15-9-ci-builds-column-validations.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/data/deprecations/15-9-ci-builds-column-validations.yml b/data/deprecations/15-9-ci-builds-column-validations.yml index 1bf6500e4c9..91a69abd08e 100644 --- a/data/deprecations/15-9-ci-builds-column-validations.yml +++ b/data/deprecations/15-9-ci-builds-column-validations.yml @@ -23,9 +23,9 @@ issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/372770 # (required) Link to the deprecation issue in GitLab body: | # (required) Do not modify this line, instead modify the lines below. Stage names are not limited like [job names](https://docs.gitlab.com/ee/ci/jobs/index.html#job-name-limitations) which have a limit of 255 characters or fewer. - - In the 16.0 milestone, the stage name limit will be enforced at 255 characters along with other text fields for new database entries in the `ci_builds` table. Users on self-managed instances that use stage names longer than 255 characters will need to shorten the job names in pipelines. After this change, existing data will not be truncated in the database. - + + In the 16.0 milestone, the stage name limit will be enforced at 255 characters along with other text fields for new database entries in the `ci_builds` table. Users on self-managed instances that use stage names longer than 255 characters will need to shorten the job names in pipelines. After this change, existing data will not be truncated in the database. +