ci: add PostHog release annotations#332
Merged
Merged
Conversation
Create a PostHog annotation on each release so version markers appear on timeline graphs. Uses the PostHog Annotations API with a personal API key (POSTHOG_PERSONAL_API_KEY secret) and project ID (POSTHOG_PROJECT_ID variable). The step is continue-on-error so annotation failures never block a release, and gracefully skips when the secrets are not configured. Signed-off-by: Rhuan Barreto <rhuan@barreto.work>
Deploying archgate-cli with
|
| Latest commit: |
dc43e38
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ae73eb0e.archgate-cli.pages.dev |
| Branch Preview URL: | https://feat-posthog-release-annotat.archgate-cli.pages.dev |
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
v0.38.0) appear as vertical lines on all timeline graphsPOST /api/projects/{id}/annotations/) withcreation_type: "GIT"for automated taggingcontinue-on-error: trueensures annotation failures never block a releaseSetup required
Two new GitHub settings must be configured before annotations appear:
POSTHOG_PERSONAL_API_KEY— a PostHog personal API key with annotations write scope (Settings → Personal API Keys)POSTHOG_PROJECT_ID— the numeric project ID from the PostHog dashboard URLTest plan
POSTHOG_PERSONAL_API_KEYandPOSTHOG_PROJECT_IDare set in the repo::notice::PostHog annotation created for v<version>