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 integrates new continuous integration (CI) workflows to enforce code style and best practices. By adding markdownlint and shellcheck, the project aims to maintain higher quality documentation and scripts, ensuring that all contributions adhere to predefined standards before being merged into the main branch.

Highlights

• New CI Workflows: Introduced CI workflows for markdownlint and shellcheck to run automatically on pull requests and pushes to the main branch, enhancing code quality and consistency.

Changelog

• .markdownlint-cli2.jsonc
  • Added configuration file for markdownlint.

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 file for markdownlint, disabling three specific rules. My review suggests that two of these rules, MD033 (inline HTML) and MD041 (first line heading), should be re-enabled to maintain higher standards for markdown quality, as their disabling does not seem justified by the current content. It's also worth noting that the pull request, titled 'add lint CI', appears incomplete as it only contains this configuration file and not the actual CI workflow for markdownlint or the mentioned shellcheck.

[CybotTM]

Closing: superseded by #6 which included the full lint workflow (markdown + yamllint + shellcheck).