Skip to content

feat(docs): redirect staging to development version#1750

Merged
JanPokorny merged 1 commit intomainfrom
janpokorny/feat-docs-redirect-staging-to-development-version
Jan 5, 2026
Merged

feat(docs): redirect staging to development version#1750
JanPokorny merged 1 commit intomainfrom
janpokorny/feat-docs-redirect-staging-to-development-version

Conversation

@JanPokorny
Copy link
Collaborator

Fixes #1738

Signed-off-by: Jan Pokorný <JenomPokorny@gmail.com>
@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Jan 5, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @JanPokorny, 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 implements a client-side redirection mechanism to improve the user experience for documentation hosted on staging environments. By automatically directing users from the 'stable' version to the 'development' version on mintlify.app staging deployments, it ensures that visitors always access the most up-to-date documentation, aligning with ongoing development efforts.

Highlights

  • New Redirection Script: A new JavaScript file, docs/redirect-staging.js, has been introduced to manage documentation redirects.
  • Staging Environment Redirection: The script specifically targets staging deployments hosted on .mintlify.app domains.
  • Stable to Development Redirect: It automatically redirects any requests to the /stable version of the documentation to the /development version within these staging environments.

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

Copy link
Contributor

@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 a client-side script to redirect from the 'stable' to the 'development' version of the documentation on staging environments. While the intent is clear, the current implementation contains a critical syntax error in the replace method's arguments, which will prevent the script from executing. I've provided a comment with a suggested fix that also improves the code's robustness by adding curly braces to the if statement.

@JanPokorny JanPokorny merged commit ce642ac into main Jan 5, 2026
7 of 8 checks passed
@JanPokorny JanPokorny deleted the janpokorny/feat-docs-redirect-staging-to-development-version branch January 5, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Default staging deployment environment to "development" docs instead of "stable"

1 participant