LilyPond Contributor's Guide: 3.3.2 Automated and manual testing

### 3.3.2 Automated and manual testing

When a merge request is opened, a bot automatically adds the `Patch::new` label to it, and it enters the countdown cycle. GitLab triggers automated testing which ensures that the patch completes `make`, `make test`, and `make doc`. Afterwards, the Patch Meister manually runs `make check` to verify regression tests. If both steps pass, the merge request is labelled `Patch::review`. On failure, the status is updated to `Patch::needs_work`.

#### LilyPond — Contributor’s Guide v2.22.2 (stable-branch).