The-DevOps-Daily / The-DevOps-Daily/devops-daily
Game: On-Call — The Daily Incident (daily Wordle-style SRE puzzle)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 392
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 121
Description
Prototype built on branch game/on-call-daily-incident (commit 785ac67). Scheduled to finish next week.
What it is
A daily, same-for-everyone production-incident puzzle. You are paged, get a 6-move budget, inspect signals and diagnose the root cause, then share a spoiler-free emoji-grid result. The Wordle loop applied to on-call: one incident a day, streaks, shareable result. Static-site safe (no backend, no auth) — daily selection is a function of the UTC date, streak lives in localStorage, share is clipboard text.
Done in the prototype
lib/on-call.ts: pure deterministic engine (daily selection, scoring, streak folding, share-grid builder) + 3 authored incidentscomponents/games/on-call.tsx: full inspect/diagnose/share UI, framer-motion + confetti- Route
app/games/on-call, registry entry, embed-route registry, OG card - 11 passing unit tests, game-registry validation green
To finish next week
- Scale incident content to ~30+ so the daily pool lasts (target a quarter)
- Optional
backup codeexport/import so a browser-data wipe doesn't lose a streak - Decide on global solve-rate ("38% solved today") — needs a tiny Cloudflare Worker + KV; defer until traffic justifies
- Screenshot/QA pass of the live game UI
- Polish: keyboard nav, reduced-motion, mobile layout check
Branch is pushed and ready to resume.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Resume from branch game/on-call-daily-incident and inspect lib/on-call.ts, components/games/on-call.tsx, and the app/games/on-call route. Run the existing 11 unit tests and game-registry validation first, then review the checklist for incident content, QA, accessibility, reduced motion, and mobile layout. Done means the live game passes those checks and the selected scope is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, game-dev, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100