Skip to content

fix: correct API Extension documentation link - #30962

Merged
asukaminato0721 merged 1 commit into
langgenius:mainfrom
Milad93R:fix/api-extension-docs-link
Jan 14, 2026
Merged

asukaminato0721 merged 1 commit into
langgenius:mainfrom
Milad93R:fix/api-extension-docs-link

Conversation

@Milad93R

Copy link
Copy Markdown
Contributor

Summary

  • Fixes the broken documentation link on the API Extension settings page
  • The old link /guides/extension/api-based-extension/README was redirecting to an unrelated getting-started page
  • Updated to point to the correct documentation URL

Fixes #30946

Test plan

  • Navigate to Settings > API Extension
  • Click "Learn how to develop your own API Extension" link
  • Verify it opens the correct API-based extension documentation page

🤖 Generated with Claude Code

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jan 14, 2026
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @Milad93R, 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 a critical user experience issue by correcting an outdated and broken documentation link within the API Extension settings. The change ensures that users seeking information on developing API Extensions are directed to the appropriate and helpful resources, thereby improving the overall usability and support for this feature.

Highlights

  • Documentation Link Fix: The pull request resolves a broken documentation link found on the API Extension settings page.
  • Incorrect Redirection: The previous link, /guides/extension/api-based-extension/README, was incorrectly redirecting users to an unrelated 'getting-started' page.
  • Updated URL: The documentation link has been updated to point to the correct and relevant API-based extension documentation URL.

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

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.

@dosubot dosubot Bot added the 📚 documentation Improvements or additions to documentation label Jan 14, 2026

@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 fixes a broken documentation link for API Extensions. The fix involves hardcoding the new URL. While this corrects the link, it removes the existing internationalization support, as the URL will now always point to the English documentation. My review includes a suggestion to update the usage of the useDocLink hook to fix the link while preserving localization, which is a more robust solution.

Comment thread web/app/components/header/account-setting/api-based-extension-page/modal.tsx Outdated
@Milad93R
Milad93R force-pushed the fix/api-extension-docs-link branch from e62be28 to 1a74b48 Compare January 14, 2026 05:32
Fixes langgenius#30946

The documentation link on the API Extension settings page was pointing to
`/guides/extension/api-based-extension/README` which redirects to an
unrelated getting-started page.

Updated to use the versioned docs URL with useDocLink hook to preserve
internationalization support.
@Milad93R
Milad93R force-pushed the fix/api-extension-docs-link branch from 1a74b48 to aa524d7 Compare January 14, 2026 06:56
@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jan 14, 2026
@asukaminato0721
asukaminato0721 merged commit 11f1782 into langgenius:main Jan 14, 2026
10 checks passed
Ssazurov pushed a commit to Ssazurov/dify that referenced this pull request Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📚 documentation Improvements or additions to documentation lgtm This PR has been approved by a maintainer size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect documentation link in "API Extension" setting page

3 participants