Skip to content
SHIFTby Guruge
All work

Developer Tools / Web Application 2026

DevPulse

A developer analytics platform, built in phases, that first pulls a developer's GitHub activity into its own database.

Year
2026
Status
In development
Platform
Web · API
Scope
Web application, API, GitHub integration
devpulse / sync
  1. 01GitHub OAuthBackend-owned handshake
  2. 02Token storageEncrypted at rest
  3. 03Repository discoveryOwned, collaborator, organisation
  4. 04Activity syncCommits, PRs, issues, reviews, releases
  5. 05Incremental runsPer-repository watermarks, idempotent
  6. 06AnalyticsNext phase

Overview

DevPulse is meant to help developers understand how they build software, not just what they built. Two of its planned phases are complete: GitHub sign-in, and synchronising repositories, languages, commits, pull requests, issues, reviews and releases into its own PostgreSQL database. The analytics layer comes next.

Challenge

Analytics are only as trustworthy as the data under them. Pulling someone's history out of GitHub means OAuth with private-repository scope, pagination, rate limits and partial failures — and a sync that can run again without duplicating anything.

Direction

Build the data layer first and make it correct. The backend owns the whole OAuth handshake and stores tokens encrypted; sync is incremental per repository and idempotent by test; the dashboard shows real sync progress rather than a spinner with a guess behind it.

What was built

  • GitHub OAuth handled entirely by the backend, with access tokens encrypted at rest
  • HttpOnly, database-backed sessions, revoked immediately on logout
  • Repository discovery across owned, collaborator and organisation repositories
  • Sync of commits, pull requests, issues, reviews, releases and languages
  • Initial and incremental sync with per-repository watermarks
  • Pagination, proactive and reactive rate-limit handling, and bounded retries
  • A dashboard “Sync now” control with real progress
  • Every query scoped by user, so no one can read or trigger another user's data

Technology

  • Next.js
  • TypeScript
  • FastAPI
  • SQLAlchemy (async)
  • PostgreSQL
  • Alembic
  • pnpm workspaces

Outcome

A tested synchronisation layer for the analytics phases to build on. GitHub is faked in the test suite, so it runs without network access or a live database.

Technical notes

  • Roadmap

    Repository health, activity timelines and developer analytics are planned phases. They are not described here as built.

Start a project

Want something like this?

Tell me about the business and what the site needs to do.