Skip to content

fix: clarify docs import LLM configuration hint - #136

Merged
Tunechi28 merged 1 commit into
Pikopod:mainfrom
deep231w:fix/docimport-llm-config-hint
Oct 14, 2026
Merged

Tunechi28 merged 1 commit into
Pikopod:mainfrom
deep231w:fix/docimport-llm-config-hint

Conversation

@deep231w

Copy link
Copy Markdown
Contributor

closes #92
What this changes

Updates the docs import error hint to mention only llm.api_key and PIKOPOD_LLM_KEY. Adds a test to verify the message.

Why

Users need clear, provider-independent instructions for configuring the LLM when importing documentation without a machine-readable spec.

Checklist

  • go test ./... -count=1 passes
  • gofmt -l cmd internal is empty and go vet ./... is clean
  • No new cgo dependency (the release artifact is a static binary on every platform)
  • Error message strings are unchanged, or the change is deliberate and called out above
  • New test fixtures have an entry in testdata/parity/importer/specs/SOURCES.md
  • No provider payloads, keys, tokens, or customer data in the diff or in test fixtures

@Tunechi28
Tunechi28 merged commit 074578a into Pikopod:main Oct 14, 2026
15 of 16 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.

Docs import hint names provider-specific env vars

2 participants