chore: disallow llms-full robots routes - #90
Open
mikemikimike wants to merge 1 commit into
Open
Conversation
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary / Problem
Closes #60 by preventing crawlers from indexing the
llms-full.txtroute and its trailing-slash variant.Changes
/llms-full.txtand/llms-full.txt/to the existingrobots.tsdisallow list.Tests
git diff --check— passed.pnpm install --frozen-lockfile --ignore-scripts --config.store-dir=D:\pnpm-store-retrywas attempted twice; dependency installation could not complete because the Windows environment encountered repeated slow registry downloads and pnpmEPERMpackage-copy failures. Formatter, lint, type-check, and build commands therefore could not run locally.Compatibility / Known limitations
This is a preventive crawler directive only; it does not change application routes or user-facing behavior. The PR targets
stagingper the repository contribution policy and does not require a changeset because it is a chore-only change.Issue: #60