skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

checking-deploy-timing

Determine when a PostHog commit shipped to an environment using GIT deploy annotations.

713|118|Updated Aug 11, 2020
Search Tags:#Deployment#annotations#gitHub#PostHog#ci cd#commit tracking#release timing
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill checking-deploy-timing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checking-deploy-timing
Source: https://github.com/PostHog/posthog-foss/tree/main/products/posthog_ai/skills/checking-deploy-timing
Command: npx skills add https://github.com/PostHog/posthog-foss --skill checking-deploy-timing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostHog staff often need to know exactly when a code change reached production in the US or EU, but deploy markers are hidden annotations that are easy to miss, and inferring timing from event volume conflates data changes with code deploys.

Core Features & Use Cases

  • Deploy Annotation Lookup: Lists hidden GIT deploy annotations via posthog:annotations-list to find when commits shipped to prod-us, prod-eu, or dev.
  • Merge Commit Correlation: Uses GitHub CLI to find a PR's merge commit and verify ancestry with the compare API so the deployed commit provably contains the change.
  • Use Case: A staff engineer asks "has my fix rolled out to prod-eu yet?" The Skill finds the PR merge commit, paginates deploy annotations around the merge time, verifies ancestry with gh api compare, and reports the exact deploy timestamp.

Quick Start

Ask when a specific PostHog PR or commit was deployed to prod-us or prod-eu and have the deploy annotations checked against the merge commit.

Frequently Asked Questions about checking-deploy-timing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check when a PostHog PR was deployed to production?▼

Find the PR's merge commit with gh pr view, then list deploy annotations using posthog:annotations-list with search "deploy". Paginate to markers around the merge time and verify the deployed commit contains the merge using the GitHub compare API.

How to tell if my commit is live in prod-us or prod-eu?▼

Match the region to its environment name: prod-us for the US and prod-eu for the EU. Check that environment's deploy annotations in chronological order after the merge and confirm ancestry with gh api repos/PostHog/posthog/compare showing behind_by of 0.

Why can't I use event volume to tell when code shipped?▼

Event volume only shows when data changed, not when code deployed. Query-runner changes apply retroactively to all data once deployed, so only the GIT deploy annotation gives the authoritative deploy time.

Why does a deploy right after my merge not include my change?▼

A deploy can fire just after a merge yet build a slightly older commit. Verify ancestry with the compare API; if behind_by is greater than 0, move to the next newer deploy of that environment and re-check.

What are the hidden GIT deploy annotations in PostHog?▼

They are organization-scoped annotations with creation_type GIT and hidden_in_user_interface true, written by CI on every deploy. Their content reads "Deployed PostHog/posthog@<sha> to <env>" and date_marker records the deploy time in UTC.

Related Skills

Explore More Software Engineering Skills→
victor-brechbillvictor-brechbill
1

merge-pr

Merge a prepared GitHub pull request via squash and clean up worktrees.

Official
Advanced
lloydchanglloydchang
2

draft-stakeholder-comms

Draft stakeholder communications for incidents, deployments, and system changes.

Community
Advanced
sergiocoding96sergiocoding96
13

market-intelligence-researcher

Aggregate Polymarket prediction data and cross-reference news sources into structured intelligence reports.

Community
Intermediate
Nice-Wolf-StudioNice-Wolf-Studio

release-management

Automate GitHub release workflows with the gh CLI.

Official
Advanced