Copy updates for PipelineTourSuccessModal
What does this MR do?
Implements Copy updates for "Success Modal" from gitlab-org/growth/product#1559 (closed)
Success Modal
Modal designs with updated copy
Paragraph 1: The pipeline will test your code on every commit. A code quality report will appear in your merge requests to warn you about potential code degradations.
Paragraph 2: Take a look at our Beginner’s Guide to Continuous Integration and our examples of GitLab CI/CD to learn more.
code quality report in paragraph 1 links to https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html
Beginner’s Guide to Continuous Integration link destination in paragraph 2 remains unchanged.
examples of GitLab CI/CD link destination in paragraph 2 remains unchanged.
Screenshots
before | after |
---|---|
![]() |
![]() |
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team