build: disable empty-lines yamllint rule

[Mesteery]

Refs: adrienverge/yamllint#444
Refs: #41981 (comment)

[tniessen]

Do you have an example where the current setting is not a good fit?

[Mesteery]

#41981 (comment)

[tniessen]

Thanks. Is there a reason to use multiple empty lines? I am no expert when it comes to YAML but it seems like there should be a way to avoid that.

[Mesteery]

Here is a site that can explain better than me: https://yaml-multiline.info.
In this example,

CLOSE_MESSAGE: > There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the [feature request management document](https://github.com/nodejs/node/blob/HEAD/doc/guides/feature-request-management.md).

becomes:

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.

[aduh95]

I don't think build: is the correct subsystem here – tools: would be a better fit imo.

[tniessen]

I don't think we should disable the rule entirely because of a single case in which it is a false positive. If no option is added to yamllint, then we should probably just keep the yamllint disable rule:empty-lines for the few valid use cases of multiple empty lines.

[github-actions]

This pull request has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.