Skip to content

Conversation

@LbsLightX
Copy link
Contributor

Fix internal documentation links to use absolute /docs/... paths as required by VitePress routing.

@gemini-code-assist
Copy link

Summary of Changes

Hello @LbsLightX, 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 an issue with internal documentation links in the Android (Termux) guide. The changes ensure that all links conform to the absolute path requirement of VitePress routing, thereby improving the navigability and correctness of the documentation for users following the guide.

Highlights

  • Documentation Link Fixes: All internal documentation links within the teldrive-on-android.md guide have been updated to use absolute paths (e.g., /docs/...) instead of relative paths.
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 correctly updates most of the internal documentation links in the Android (Termux) guide to be absolute paths, which is great for routing consistency in VitePress. However, I noticed one link where the update seems to have been applied incorrectly, adding a slash to the link text instead of the URL path. I've left a suggestion to correct this. Otherwise, the changes look good.

### Basic `config.toml` (Recommended for New Users)

1. First, read the [usage documentation](docs/getting-started/usage) for configuring a Supabase database.
1. First, read the [/usage documentation](docs/getting-started/usage) for configuring a Supabase database.

Choose a reason for hiding this comment

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

medium

It looks like the forward slash was accidentally added to the link text instead of the URL path, and the path itself wasn't made absolute. To make this an absolute link consistent with the other changes, the path should start with /docs/....

Suggested change
1. First, read the [/usage documentation](docs/getting-started/usage) for configuring a Supabase database.
1. First, read the [usage documentation](/docs/getting-started/usage) for configuring a Supabase database.

@LbsLightX LbsLightX closed this Jan 7, 2026
@LbsLightX LbsLightX reopened this Jan 7, 2026
@LbsLightX
Copy link
Contributor Author

Reopening sorry about that
The PR now updates all internal links to absolute /docs/... paths.

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