Re: CI doesn't catch changes in autogenerated documentation

[David Kastrup]

David Kastrup <dak@gnu.org> writes:

> I just had the pipeline run
>
> https://gitlab.com/lilypond/lilypond/-/pipelines/393509219
>
> finish.  This change adds engravers/performers including engraver
> information, stuff that is extracted into the IR.  It also adds a
> regtest.
>
> However, the CI decided to skip generation of the documentation which
> presumably means that the documentation will not be updated until after
> some other change adds documentation.

Wait: I don't see any documentation run for a master merge in the last
week.  Does the master merge take the artifacts generated by the final
test run of the branch instead?

In that case, this report would be invalid.

-- 
David Kastrup