On 4/9/2018 4:51 PM, Carl Sorensen wrote:
The problem with this workflow is that the merger is the person who needs to do 
the squash-and-merge.  That's extra work for the merger.  I'd prefer to keep 
the work on the patch creator.

GitLab actually gave me the "squash" option at both points, requesting and accepting the merge.


"Anyone who can create or edit a merge request can choose for it to be squashed on the merge request form."

"This can then be overridden at the time of accepting the merge request"
Karlin High
Missouri, USA

lilypond-devel mailing list

Reply via email to