Skip to content

chore: add YAML linting to CI#8

Merged
CybotTM merged 2 commits intomainfrom
chore/add-yamllint
Feb 15, 2026
Merged

chore: add YAML linting to CI#8
CybotTM merged 2 commits intomainfrom
chore/add-yamllint

Conversation

@CybotTM
Copy link
Copy Markdown
Member

@CybotTM CybotTM commented Feb 15, 2026

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

Changes

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

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @CybotTM, I'm Gemini Code Assist1! 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 integrates YAML linting into the project's continuous integration process. By adding yamllint and a custom configuration, it aims to enforce consistent formatting and catch potential issues in YAML files, thereby improving overall code quality and maintainability.

Highlights

  • YAML Linting: Introduced yamllint to the CI workflow to validate YAML files, enhancing code quality and consistency.
  • Configuration: Added a .yamllint.yml configuration file, disabling line-length, truthy, document-start, and comments-indentation rules to tailor linting behavior.
Changelog
  • .yamllint.yml
    • Added a new configuration file for yamllint.
    • Disabled line-length, truthy, document-start, and comments-indentation rules to customize linting behavior.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/lint.yml
Activity
  • No specific activity (comments, reviews, progress) has been recorded for 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.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds YAML linting to the CI pipeline by introducing a .yamllint.yml configuration file. The configuration extends the default settings but disables several useful rules. My review includes a suggestion to re-enable some of these rules to improve code consistency and readability across YAML files in the repository.

@CybotTM CybotTM merged commit 4b73446 into main Feb 15, 2026
5 checks passed
@CybotTM CybotTM deleted the chore/add-yamllint branch February 15, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant