docs: clarify required vs optional API keys in .env setup (#3844)#4112
Open
xingzihai wants to merge 1 commit into
Open
docs: clarify required vs optional API keys in .env setup (#3844)#4112xingzihai wants to merge 1 commit into
xingzihai wants to merge 1 commit into
Conversation
xingzihai
had a problem deploying
to
external-pr-scan
GitHub Actions
Failure
github-actions
Bot
added
documentation
This was referenced Apr 2, 2026
This was referenced Apr 9, 2026
This was referenced Apr 22, 2026
Closed
Closed
This was referenced Apr 29, 2026
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
1 participant
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.
Fixes #3844
Clarifies which API keys are required vs optional in the .env setup documentation to help users understand configuration requirements.