zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.4 KiB
Engineering analytics fixtures
A bounded, real snapshot of Insights/insights GitHub data (recent pull requests + workflow runs), trimmed to the fields the curated warehouse views read. Used to get realistic data into a local stack without connecting a live GitHub warehouse source.
Refresh the snapshot
Requires an authenticated gh CLI; roughly 160 API requests with the default caps.
python products/engineering_analytics/fixtures/fetch.py
Load into a local stack
With the dev stack running (Datastore + object storage):
python manage.py seed_engineering_analytics --team-id 1
Creates the github_pull_requests, github_workflow_runs, github_workflow_jobs, and github_team_members warehouse tables for the team (CSV-backed, same mechanism as the demo data generator), plus per-test CI spans in Traces (flaky tests, team CI health) and thinned CI failure lines in Logs (broken tests, per-run failure logs).
The sidebar entry is gated on the engineering-analytics feature flag, and local dev evaluates flags against your local project (SELF_CAPTURE) — create an active boolean flag with that key in your local project to see the product.
Timestamps are rebased so the newest row lands at "now" (the product's queries window on server-side now()); pass --keep-dates for the faithful snapshot.
Re-running replaces the previously seeded tables; tables owned by a real connected GitHub source are never touched.