Draft: Update rules failure reason format
What does this MR do and why?
Corrects formatting for failure message when displayed in an alert. System notes remain unaffected.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
![]() |
![]() |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
For New Pipeline Alerts
- Update pipeline configuration to not run fail due to workflow rules or rules:
stages: # List of stages for jobs, and their order of execution
- build
- test
- deploy
workflow:
rules:
- if: $CI_COMMIT_MESSAGE =~ /-draft$/
when: never
- Create an MR with the word "draft" in the commit message and merge to main
- navigate to
http://localhost:3000/gitlab-org/merge-train-experiments/-/pipelines/new
(or whatever your local gdk is) - run a pipeline and observe the failure message
For System notes validation:
Follow these validation steps
Related to #477828
Edited by Vlad Wolanyk