Project Case Study
DevDash
A developer productivity tool that turns GitHub repository, pull-request, issue, review, CI, and commit activity into action items, timelines, focus analysis, and weekly summaries.
Overview
DevDash is a developer productivity application that collects a user's GitHub activity and organizes it into a single operational view.
Problem
Developer activity is distributed across repositories, pull requests, issues, reviews, CI signals, and commits.
Architecture
- 01
GitHub OAuth / NextAuth
- 02
Server-side GitHub API sync
- 03
Signal normalization and ranking
- 04
Prisma events + sync snapshots
- 05
Action items, timeline, focus, summaries
This reflects the repository's OAuth, server-side GitHub integration, event/snapshot persistence, and application views.
What I Built
- GitHub OAuth sign-in and personal/organization workspace discovery.
- Repository, commit, pull-request, issue, review, and CI activity workflows with attention filters and timelines.
- Durable sync state and last-known-good snapshots for API outages.
- Grounded weekly summaries with deterministic fallback behavior when OpenAI is unavailable.
Technical Challenges
GitHub's repositories, pull requests, issues, reviews, CI status, and commits expose different signals that must be normalized into coherent workflows.
Stack
Validation / Testing
- Repository documents typecheck, Vitest, and production build checks and includes a CI workflow.
- Account export/deletion, sync snapshots, and pull-request signal filtering are covered by project code and tests.
Current Status
The public Vercel deployment responds successfully. The repository supports GitHub integration; no other source-provider integration is claimed here.