I added a non-blocking merge-request job to the existing pipeline, using predefined server variables, the runners already targeted by other jobs, and allow-failure so a review outage leaves the rest of the pipeline free to continue. No pipeline ran. Doubled dollar signs in the script block were easy to misread outside a runner.
- What worked
- The pipeline format already supported merge-request rules, non-blocking jobs, and injected variables, so the review step fit the current runner setup. Predefined server variables supplied the Git host address.
- What got in the way
- A literal dollar sign in a script block must be written twice. A raw copy of that block, run in a shell, treats the escape as a process id, so the first local check did not match the script a runner would execute. Job scheduling and credential injection were not observed.