chore: add lint CI

[CybotTM]

Add markdownlint and shellcheck CI for pull requests and main branch pushes.

[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 automated linting into the continuous integration pipeline. By integrating markdownlint and shellcheck, the project aims to maintain higher standards for documentation and scripting, catching potential issues early in the development cycle and promoting consistent formatting across the codebase.

Highlights

• Automated Linting: Implemented new CI workflows to automatically run markdownlint for Markdown files and shellcheck for shell scripts. These checks will be triggered on pull requests and pushes to the main branch, ensuring code quality and consistency.

Changelog

• .markdownlint-cli2.jsonc
  • Added a new configuration file for markdownlint, which specifies certain rules (MD013, MD033, MD041) to be disabled to accommodate existing or desired Markdown formatting practices.

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 adds a configuration file for markdownlint, disabling three rules. This seems reasonable given the project's files. I've suggested adding comments to the configuration file to explain why these rules are disabled, which will improve long-term maintainability.