pulse is now a static, theme-first standup review tool.
Instead of randomizing speakers and collecting survey data, the new flow is:
- Pull the last day of in-scope GitHub activity for the team with
gh - Roll the resulting work into a small set of standup themes
- Review those themes in the app before going person-by-person
Generate the daily digest:
npm run standup:generateThat writes a local build artifact at public/data/standup-report.json, which the app reads directly.
Then run the app locally:
npm install
npm run devThe generator reads public/data/team-members.json.
That file controls:
- which GitHub users are included
- which orgs or repos count as “in scope”
- repo-level fallback topics
- keyword rules used to cluster work into shared standup topics
The efficient path for PE standup is not “one random person at a time.” It is:
- theme-first review so related work gets discussed together without exploding into dozens of one-off sections
- raw per-person activity kept available as a secondary check
- static JSON output so you can regenerate with a script, inspect it with Codex, and ship it to GitHub Pages without a backend
The app is still a static Next.js export deployed via GitHub Pages from main.
The Pages workflow now regenerates the standup digest during build, so the deployed site does not depend on a committed daily JSON snapshot.
There is also a pull-request preview workflow for Vercel in .github/workflows/vercel-preview.yml. To enable it, add these repository secrets:
VERCEL_TOKENVERCEL_ORG_IDVERCEL_PROJECT_ID
The workflow builds in GitHub Actions, runs npm run standup:generate there, and deploys the prebuilt output to a Vercel preview URL. It skips automatically for forked pull requests or when the Vercel secrets are missing.