chore: add YAML linting to CI

[CybotTM]

Add lint CI workflow with markdown, yamllint, and shellcheck jobs.

Changes

• Add .yamllint.yml config (disables line-length, truthy, document-start, comments-indentation rules)
• Add .github/workflows/lint.yml with markdown, yamllint, and shellcheck jobs

[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 foundational changes for YAML linting by adding a dedicated configuration file. The primary goal is to establish consistent styling and error checking for YAML files, thereby enhancing code quality and maintainability. The configuration is tailored to disable certain rules, allowing for flexibility while still enforcing overall best practices.

Highlights

• YAML Linting Configuration: A new .yamllint.yml configuration file has been added to define the rules for YAML linting. This configuration specifically disables checks for line-length, truthy values, document-start markers, and comments-indentation.

Changelog

• .yamllint.yml
  • Added a new configuration file for yamllint.

Ignored Files

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

Activity

• No human activity has been recorded on this pull request yet.

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 adds a configuration file for yamllint to introduce YAML linting into the CI process. This is a positive change for code quality. The current configuration disables several rules. I've suggested re-enabling the truthy and comments-indentation rules to enforce a more consistent and readable style for YAML files across the repository.

[gemini-code-assist]

It's recommended to keep the truthy and comments-indentation rules enabled. The truthy rule enforces standard true/false booleans, which improves clarity and interoperability. The comments-indentation rule is helpful for maintaining a consistent code style. Disabling them might lead to inconsistent and harder-to-read YAML files.

  line-length: disable
  document-start: disable