YAML Lint Errors Causing CI Job Failure

[quiet-node]

Description

Currently, the charts CI job fails due to lint errors in YAML files. The errors include:

• Incorrect comment formatting: “too few spaces before comment” (e.g., lines 71 and 177).
• Failed linting process: The validation of Helm charts (hedera-json-rpc-relay and hedera-json-rpc-relay-websocket) fails, causing the CI pipeline to exit with status code 1.

The error details are visible in GitHub Actions logs and can be reproduced by running the linting process locally.

Steps to Reproduce

1. Push changes or trigger a GitHub Actions workflow that includes YAML linting.
2. Observe the failure in the linting step for values.yaml.

Proposed Solution

• Fix comment formatting issues by ensuring proper spacing before comments in YAML files.
• Maybe move the comment to the top of the statement instead of the side

For example, instead of

postman: '' # Custom postman.json in base64 encoding

Move it to the top

# Custom postman.json in base64 encoding
postman: ''

[Ferparishuertas]

Options

• Skip husky for charts
• Change linter to allow husky style
• Move the comments on top --> Chosen solution