-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
Summary:
In a GitLab.cee Pipelines-as-Code (PaC) nudging automerge scenario, when a PipelineRun is manually canceled, the corresponding merge request (MR) is sometimes automatically merged.
The expected behavior is that the MR should remain open, since its associated check (PipelineRun) did not complete successfully.
It appears that PaC reports the pipeline status as "cancelled" (with two Ls), while GitLab expects "canceled" (with one L). Due to this mismatch, GitLab might not correctly interpret the canceled state, allowing the MR to be auto-merged even though the pipeline was canceled.
Expected Behavior:
- When a PipelineRun is canceled, the GitLab MR should remain open and not auto-merge.
- PaC should report the canceled status in a format recognized by GitLab ("canceled").
Actual Behavior:
- The PipelineRun is canceled, but the MR is automatically merged in GitLab.
- GitLab appears to misinterpret the reported status from PaC.