Enable PostHog build events on main - #74
Merged
Merged
Conversation
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.
The merged PostHog client had no workflow supplying its project token, so all CI captures were disabled. Add a dedicated workflow on main pushes and manual runs that installs dependencies, reads the POSTHOG_API_KEY secret and POSTHOG_HOST variable, and runs the index and SEO generators.
Uses read-only repository permissions, disables persisted checkout credentials, and limits execution to main. Generated files remain on the runner. Existing pull request jobs remain analytics-free. Uses a stable github-actions identity for build events.
Validation: YAML parsed locally and git diff --check passed. Repository token and US ingestion host were configured through the GitHub settings UI. End-to-end event verification follows the first main-branch run.