Re: automatically setting 'Patch::review' for MRs?
Colin Campbell <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2025-07-22 21:25, Werner LEMBERG wrote:
> In section 1.3 of the CG ('Summary for experienced developers') we
> have the following item:
>
> 2. A Merge Request is usually automatically tested within an hour
> of submission. Once it has passed the basic tests – ‘make
> check’, ‘make’, ‘make doc’ – the tracker will be updated and
> the patch’s status will change to ‘Patch::review’ for other
> developers to examine.
>
> However, this automatic tracker update doesn't happen currently; we
> have to set 'Patch::review' manually.
>
> Does gitlab support such an automatical setting of a label? If yes,
> it would be great if this can be (re)activated. Otherwise we have to
> update the documentation...
>
>
> Werner
FWIW, I have been checking Patch::New and advancing MRs to Review
manually, per CG 3.3.2, which is a more explicit presentation of CG
1.3. It's gratifying but quite rare that I catch anything in reg tests
at the New stage. The wording of CG 1.3 implies eliminating the New
stage, which might not be a bad thing: New and Review aren't that
different, really.
Colin