Here is the current countdown report.
Ther next countdown will begin on September 30th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1642 Doc: Replace \mark with \textMark/\textEndMark in
examples -
>> [...] – we could add `[skip ci]` to avoid that. Shall I do that
>> for this commit and similar ones in the future?
>
> Can you make it so that it'll skip CI in the initial MR upload and
> in subsequent iterations, but still spawn a pipeline when merging?
Is this possible? AFAIK, there is
Jean Abou Samra writes:
> Le 27/09/2022 à 17:39, Werner LEMBERG a écrit :
>> I've just submitted
>>
>>https://gitlab.com/lilypond/lilypond/-/merge_requests/1643
>>
>> to improve `makelsr.pl`. Running CI for this MR is a waste of
>> resources because this script is not part of the normal
Le 27/09/2022 à 17:39, Werner LEMBERG a écrit :
I've just submitted
https://gitlab.com/lilypond/lilypond/-/merge_requests/1643
to improve `makelsr.pl`. Running CI for this MR is a waste of
resources because this script is not part of the normal build and test
cycle – we could add `[skip
Le 27/09/2022 à 22:07, Jean Abou Samra a écrit :
Le 27/09/2022 à 21:05, Thomas Morley a écrit :
Hi Jean,
will do.
Is it urgent? I'll have not much time before weekend.
By the way, it would be great if I could submit the
edits myself to LSR, but I haven't found a way to do
so. Apparently, I
