chore: add YAML linting to CI

[CybotTM]

Add yamllint to the lint CI workflow to validate YAML files.

[gemini-code-assist]

Summary of Changes

Hello @CybotTM, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces yamllint to the continuous integration pipeline, enhancing code quality by automatically checking YAML files for common issues and style inconsistencies. This ensures that all YAML configurations adhere to a consistent standard, improving maintainability and reducing potential errors.

Highlights

• YAML Linting Introduction: Integrated yamllint into the CI workflow to automatically validate YAML file syntax and style, ensuring consistency across the repository.
• Configuration for yamllint: Added a .yamllint.yml configuration file to disable specific rules such as line-length, truthy, document-start, and comments-indentation for tailored linting behavior.

Changelog

• .yamllint.yml
  • Added a new configuration file for yamllint to define linting rules.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/lint.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a configuration for yamllint. However, it disables several useful linting rules by default. My feedback suggests adopting a stricter configuration to ensure YAML files are consistent and to prevent potential issues. Specifically, I've recommended adjusting the line-length rule instead of disabling it, and re-enabling other rules like truthy for better code quality.