Skip to content

Conversation

@nithishr
Copy link
Contributor

@nithishr nithishr commented Oct 23, 2025

…r based tutorial naming
We need to do this as otherwise we will end up with duplicate copies of the tutorials like reported in https://jira.issues.couchbase.com/browse/DA-1177

@nithishr nithishr requested a review from a team as a code owner October 23, 2025 16:05
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @nithishr, 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 focuses on cleaning up the project's tutorial section by removing numerous autogenerated markdown files. This essential step paves the way for adopting a more structured, folder-based naming system for tutorials, which will enhance content organization and maintainability.

Highlights

  • Removal of Autogenerated Tutorials: This pull request removes a significant number of autogenerated tutorial markdown files from the tutorial/markdown/generated/vector-search-cookbook/ directory.
  • Enabling Folder-Based Naming: The removal of these files is a prerequisite step to facilitate the implementation of a new folder-based naming convention for tutorials, as indicated by the pull request title and description.
  • Tutorial Content Restructuring: This change suggests a broader restructuring effort to improve the organization and management of tutorial content within the project.
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 removes a number of autogenerated tutorial markdown files from the tutorial/markdown/generated/vector-search-cookbook/ directory. This change appears to be a preparatory step for implementing a new folder-based naming convention for tutorials, as suggested by the pull request's title. The removal of these generated files is appropriate, and the changes look correct.

@nithishr nithishr merged commit fc4a83e into main Oct 23, 2025
4 checks passed
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