-
Notifications
You must be signed in to change notification settings - Fork 1
Generate llms.txt files on build for LLM reference #1404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Added `docusaurus-plugin-llms` version 0.1.5 to enable new plugin functionality.
Integrated `docusaurus-plugin-llms` with configuration options for generating LLMs text files and content cleaning. Also corrected the tagline capitalization for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @josh-wong, 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!
I've introduced a new Docusaurus plugin, "docusaurus-plugin-llms", to automatically generate "llms.txt" and "llms-full.txt" files during the build process. These files will contain structured information from our documentation, adhering to the LLMs.txt format, to facilitate consumption by large language models.
Highlights
- New Plugin Integration: I've added "docusaurus-plugin-llms" as a dependency and configured it within our Docusaurus setup.
- Automated LLM File Generation: This plugin is set up to generate "llms.txt" (titles and links) and "llms-full.txt" (full content) from the latest version of our documentation.
- Content Cleaning Configuration: I've configured options like "excludeImports", "removeDuplicateHeadings", and "includeUnmatchedLast" for content cleaning, though I've noted that "excludeImports" and "removeDuplicateHeadings" currently have known issues that may require a plugin upgrade.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 or fill out our survey to provide feedback.
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
-
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. ↩
There was a problem hiding this 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 the docusaurus-plugin-llms to generate llms.txt files for Large Language Models. The changes look good, and I've added a couple of minor suggestions to improve the maintainability of the configuration file. Specifically, I've pointed out duplicated configuration values and suggested consolidating some comments.
Description
This PR introduces a new plugin,
docusaurus-plugin-llms, to the Docusaurus configuration and updates thepackage.jsonfile to include the plugin as a dependency. The plugin is configured to generate the following files on build:These generated files adhere to the current format for LLMs.txt files.
Related issues and/or PRs
Changes made
docusaurus-plugin-llmstopackage.json: Included the plugin version^0.1.5as a dependency. (package.jsonR36)docusaurus-plugin-llmstodocusaurus.config.js: Configured the plugin with options to generatellms.txtandllms-full.txt, specify thedocsdirectory, and enable content cleaning features like removing duplicate headings and including unmatched last headings. Some options are noted to have issues that may require a plugin upgrade. (docusaurus.config.jsR282-R296)Checklist
Additional notes (optional)
N/A