Skip to content

Add the new possible values for the detailed_merge_status api field

What does this MR do and why?

Add the new possible values for the detailed_merge_status api field which were missed in: !144729 (merged)

Related to #444287 (closed)

Edited by Marc Shaw

Merge request reports