zeekayandHanzo Dev
841ea1c0da
716 files rewritten, 30 renamed, same family mapping as the frontend pass.
Held back, and each for a reason rather than by oversight:
db_table values insights_hogfunction, insights_hogflow,
insights_hogfunctiontemplate, hogflow_templates.
Renaming a table is ALTER TABLE, so it ships as a
migration with the raw SQL in nodejs that names it.
hog_invocation_results a Datastore table with Kafka engine tables on it
products/review_hog the module path is the Django app path; moving it
moves app_label and every migration is recorded under
(app_label, name). That is the same history break as
renaming a migration file, one level up.
*/migrations/* five files, untouched
whogho an integration vendor
Checked: 395 of 397 changed Python files compile. The two that do not —
insightsql/database/database.py and temporal/schedule.py — fail identically at
origin/main under the same interpreter, because they use `type X = ...` and
`except*`, which need the 3.13 this repo pins and not the 3.9 doing the check.
Running the check against the original is what told those apart from a real
break.
Co-authored-by: Hanzo Dev <[email protected]>
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.