Skip to content

docs: add missing .md extensions to six cross-reference links#28505

Open
ZayanKhan-12 wants to merge 1 commit into
google-gemini:mainfrom
ZayanKhan-12:fix-extensionless-doc-links
Open

docs: add missing .md extensions to six cross-reference links#28505
ZayanKhan-12 wants to merge 1 commit into
google-gemini:mainfrom
ZayanKhan-12:fix-extensionless-doc-links

Conversation

@ZayanKhan-12

Copy link
Copy Markdown

Six cross-references in docs/reference/policy-engine.md (5) and docs/hooks/reference.md (1) link other doc pages extensionless — four also with site-absolute /docs/... paths — e.g. ](/docs/reference/tools#available-tools) and ](../reference/tools). On GitHub's rendered view these 404 (docs/reference/tools has no extensionless file). The other 57 cross-references in the same directories consistently use relative .md links, and both targets (docs/reference/tools.md, docs/tools/shell.md) exist — so this normalizes the stragglers to the dominant convention. Anchors preserved.

Docs only; no code changes.

🤖 Generated with Claude Code

@ZayanKhan-12
ZayanKhan-12 requested review from a team as code owners July 22, 2026 18:57
@gemini-code-assist

Copy link
Copy Markdown
Contributor

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 addresses broken cross-reference links within the documentation. By appending the necessary .md extensions and standardizing path formats, it ensures that users can correctly navigate between related documentation pages without encountering broken links.

Highlights

  • Documentation Fixes: Corrected six cross-reference links in the documentation by adding missing .md file extensions to ensure proper navigation and prevent 404 errors.
  • Path Normalization: Updated absolute site paths to relative paths to maintain consistency with the existing documentation structure.
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 the 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 counterproductive. 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.

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.

@github-actions github-actions Bot added the size/s A small PR label Jul 22, 2026
@github-actions

Copy link
Copy Markdown

📊 PR Size: size/S

  • Lines changed: 12
  • Additions: +6
  • Deletions: -6
  • Files changed: 2

@google-cla

google-cla Bot commented Jul 22, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

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

Copy link
Copy Markdown
Contributor

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 updates several internal documentation links in docs/hooks/reference.md and docs/reference/policy-engine.md to use correct relative paths with .md extensions instead of absolute or extensionless paths. There are no review comments, and I have no feedback to provide.

Note: Security Review has been skipped due to the limited scope of the PR.

@ZayanKhan-12
ZayanKhan-12 force-pushed the fix-extensionless-doc-links branch from daade18 to 63b6fb8 Compare July 22, 2026 19:03
@ZayanKhan-12

Copy link
Copy Markdown
Author

@googlebot I signed it!

policy-engine.md and hooks/reference.md link docs pages without the
.md extension (and with site-absolute /docs/ paths), unlike the 57
other cross-references in these directories; on GitHub's rendered
view these 404. Point them at the .md files directly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/s A small PR status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants