Skip to content

fix: add link-check ignore patterns for localhost and private URLs#1129

Merged
GrammaTonic merged 1 commit intodevelopfrom
fix/link-check-ignore-patterns
Mar 1, 2026
Merged

fix: add link-check ignore patterns for localhost and private URLs#1129
GrammaTonic merged 1 commit intodevelopfrom
fix/link-check-ignore-patterns

Conversation

@GrammaTonic
Copy link
Owner

Adds ignore patterns to .markdown-link-check.json for:

  • http(s)://localhost URLs (documentation examples, unreachable in CI)
  • https://github.com/users/*/projects/ URLs (private project boards, return 404 in CI)

Fixes the docs-validation failure on PR #1128 (develop to main promotion).

Add ignore patterns for localhost URLs (documentation examples not
reachable in CI) and GitHub user project board URLs (private/404 in CI).
Fixes docs-validation failure on PR #1128.
@gemini-code-assist
Copy link

Summary of Changes

Hello, 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 enhances the documentation link validation process by introducing new ignore patterns. It addresses CI failures caused by unreachable localhost URLs and inaccessible private GitHub project board links, ensuring that the link checker focuses only on publicly accessible and valid external links.

Highlights

  • Ignore localhost URLs: Added a pattern to .markdown-link-check.json to ignore http(s)://localhost URLs, which are often used in documentation examples but are unreachable in CI environments.
  • Ignore private GitHub project URLs: Added a pattern to .markdown-link-check.json to ignore https://github.com/users/*/projects/ URLs, which correspond to private project boards and typically return 404 errors in CI.

🧠 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.

Changelog
  • .markdown-link-check.json
    • Added ignore patterns for localhost and private GitHub project URLs.
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

@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 ignore patterns to the markdown link checker configuration to avoid failures on localhost and private GitHub project URLs, which are unreachable in CI. The change is correct and addresses the issue. I've suggested a minor improvement to make the localhost pattern more robust to cover more edge cases.

"pattern": "^https://github\\.com/users/.*/projects/"
},
{
"pattern": "^https?://localhost[:/]"

Choose a reason for hiding this comment

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

medium

The regular expression ^https?://localhost[:/] is a bit restrictive. It will not match a URL that is just http://localhost without a trailing port or path. Using a word boundary (\b) would make this pattern more robust, correctly matching localhost as a whole word in various URL formats (e.g., with a port, with a path, or standalone) while avoiding matches for hostnames that merely start with localhost.

Suggested change
"pattern": "^https?://localhost[:/]"
"pattern": "^https?://localhost\\b"

@GrammaTonic GrammaTonic merged commit c9a28f8 into develop Mar 1, 2026
1 check passed
@GrammaTonic GrammaTonic deleted the fix/link-check-ignore-patterns branch March 1, 2026 21:56
@GrammaTonic GrammaTonic mentioned this pull request Mar 1, 2026
3 tasks
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