Story URLs now include a readable slug derived from the headline, replacing opaque identifiers with paths like /stories/pr-123/adding-user-authentication/ that search engines can parse.
The static site now speaks the language of search engines and social platforms—canonical URLs, OG images, Twitter cards, and JSON-LD structured data ship on every page.
Story pages now display author names as plain @mentions instead of clickable links, standardizing how attribution appears across the site.
Direct-push commits can now display verified GitHub usernames with working profile links instead of falling back to plain display names.
The site now shows a proper branded logo with a recognizable pulse glyph, and visitors can switch between light, dark, or system theme—with their preference saved for return visits.
GitHub Actions runs now fetch the prior manifest from the deployed site and only process new commits — daily digests scale with velocity instead of repository history depth.
Development activity feeds now display as an editorial publication with a proper masthead, day-grouped stories, and tiered presentation for features, fixes, and housekeeping changes.
Gitpulse gets a full editorial redesign with a sticky header, repository headers displaying real GitHub descriptions, and a visual size indicator replacing text labels.
GitPulse's commit analysis now runs concurrently — multiple commits are processed simultaneously rather than one after another, dramatically reducing runtime for repositories with many commits.
GitHub actions now detect whether commits came through a pull request and enrich each story with linked issues, accurate diff stats, and a size classification — no more guessing whether a change was a direct push or a merged PR.
Commits analyzed by gitpulse now produce full TechCrunch-style editorial copy — with headlines, story body, category classification, and a fact-check flag — instead of plain summaries.
The gitpulse GitHub Action now reads local commit history, asks an LLM to write a journalistic story for each commit, and outputs Story JSON. Works with any OpenAI-compatible endpoint.
GitPulse can now render development activity as editorial stories — new content collection reads JSON files to power a feed page and individual story pages, with static generation at build time.