chore: ignore 429 (too busy) responses from github w/ markdown link checker

[kevmoo]

Also remove unused .markdownlint.yaml file

[gemini-code-assist]

Summary of Changes

Hello @kevmoo, 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 focuses on maintenance and cleanup tasks. It introduces a configuration change to the markdown link checker to gracefully handle GitHub API rate limits, thereby improving the reliability of link validation. Concurrently, it streamlines the repository by removing an unnecessary markdown linter configuration file, contributing to a cleaner and more efficient project setup.

Highlights

• Markdown Link Checker Configuration: A new configuration file, .github/markdown-link-check-config.json, has been added. This configuration instructs the markdown link checker to ignore HTTP 429 (Too Many Requests) responses specifically for links pointing to https://github.com. This change aims to prevent build failures caused by GitHub API rate limiting during link checks.
• Removal of Unused Markdown Linter Configuration: The .markdownlint.yaml file has been removed from the repository. This file was identified as unused, indicating a cleanup of obsolete configuration.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/markdown_linter.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 the markdown link checker to ignore 429 (Too Busy) responses from GitHub, which is a good measure to prevent CI failures due to rate limiting. It also removes an apparently unused .markdownlint.yaml file, which is good repository hygiene. I've found one minor issue in the new configuration file regarding an unescaped character in a regular expression and have provided a suggestion to fix it. Otherwise, the changes look good.