Skip to content

Conversation

@Killusions
Copy link
Member

@Killusions Killusions commented Jan 9, 2026

Only for testing #752


@gemini-code-assist
Copy link

Summary of Changes

Hello @Killusions, 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 introduces a comprehensive system for managing and displaying versioned documentation. It includes a backend script to consolidate version metadata, a frontend script to ensure users are directed to the most current documentation by default, and updates to the MkDocs configuration to enable these features. The primary goal is to enhance the discoverability and organization of different documentation versions.

Highlights

  • Documentation Version Management Script: A new Node.js script, .github/scripts/merge-versions.mjs, has been added. This script is responsible for merging existing documentation version data (e.g., from S3) with newly deployed versions into a versions.json file. It ensures that the documentation's version selector accurately reflects all available versions and sorts them logically (latest, preview, then descending by major version).
  • Client-Side Version Redirection: A new JavaScript file, docs/_src/js/version-redirect.js, has been introduced. This script handles automatic redirection for documentation paths. If a user accesses the root path or a non-versioned path, they will be automatically redirected to the /latest/ version of the documentation. This redirection is intelligently disabled for local development environments.
  • MkDocs Configuration Update: The mkdocs.yml configuration file has been updated to integrate the new versioning features. The version-redirect.js script is now included in extra_javascript, ensuring it runs on the documentation site. Additionally, a new extra.version section has been added, configuring the mike provider for version management with latest set as the default documentation version.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/publish-documentation.yaml
    • .github/workflows/release.yaml
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 introduces versioning for the documentation by adding a script to merge version files, a client-side script for redirection, and updating the mkdocs.yml configuration. The changes are well-structured. I've provided a few suggestions to improve code clarity and reduce duplication in the new scripts for better long-term maintainability.

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

@Killusions Killusions force-pushed the chore/add-versioned-documentation-with-auto-detection-in-docs-main branch from 37488f2 to 364b865 Compare January 9, 2026 19:59
@Killusions
Copy link
Member Author

Killusions commented Jan 15, 2026

@spliffone This is not the right PR but I also fixed them on #752

@Killusions Killusions force-pushed the chore/add-versioned-documentation-with-auto-detection-in-docs-main branch from 364b865 to 9783345 Compare January 16, 2026 16:04
@Killusions
Copy link
Member Author

Tested and works, closing

@Killusions Killusions reopened this Jan 21, 2026
@Killusions Killusions force-pushed the chore/add-versioned-documentation-with-auto-detection-in-docs-main branch from 9783345 to f441fec Compare January 21, 2026 15:45
@github-actions
Copy link

Code Coverage

@Killusions
Copy link
Member Author

Works again, closing

@Killusions Killusions closed this Jan 21, 2026
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.

3 participants