glab mr view now reports 'unknown' for merge request conflicts while GitLab is still checking
A change to the GitLab CLI (glab) addresses a gap where redirecting mr view output to a file dropped the conflict status shown in the interactive view. The plain-text output now prints a conflicts line with true, false, or unknown, where unknown covers the pending merge-status states unchecked, checking, and preparing. The formatter checks detailed_merge_status before rendering the boolean, since a false value during calculation could mislead scripts. Automation is advised to read the existing JSON fields instead of grepping the text output, and to retry within a bounded timeout when the status is pending. Regression tests cover the true, false, and pending cases, and the change was verified with passing tests and GitLab CI.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.



Discussion (0)
Log in to join the discussion and vote.
Log in