Translate content: PostHog key safety clarification - #6920
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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
Translate the PostHog API key safety note added in #6918 into Spanish, French, and Chinese.
Changes
es/integrations/analytics/posthog.mdx: add clarification that the PostHog project API key is a public client-side token, safe to commit.fr/integrations/analytics/posthog.mdx: same clarification, French.zh/integrations/analytics/posthog.mdx: same clarification, Chinese.Context
Mirrors the English change from #6918 (Clarify PostHog key safety).
Note
Low Risk
Documentation-only i18n additions with no code or configuration behavior changes.
Overview
Adds a short note under the
apiKeyconfiguration field in the Spanish, French, and Chinese PostHog integration pages, matching the English clarification from #6918.The new copy explains that the PostHog project key is a public client-side token (the same one sent with browser analytics events) and that it is safe to commit in the documentation repo.
Reviewed by Cursor Bugbot for commit b8f4bba. Bugbot is set up for automated code reviews on this repo. Configure here.