Gitpulse
The Gitpulse Dispatch
Monday, May 11, 2026

The Gitpulse Dispatch

Development activity intelligence for gitpulse itself

Monday, May 11, 2026

New Feature·Merged May 11, 2026·M

Image storage layer arrives with Vercel Blob

#52·by @znat

A pluggable storage interface lands in the CLI, giving the codebase a home for binary assets like AI-generated PR images. Vercel Blob is the first shipped provider.

Sunday, May 10, 2026

Saturday, May 9, 2026

New Feature·Merged May 9, 2026·M

JSON data exposed at human-readable URLs

#48·by @znat

JSON data for pull requests, commits, and releases is now accessible at clean URLs that mirror the site routes — no more digging through nested manifest paths.

Fixes & Patches

Friday, May 8, 2026

Thursday, May 7, 2026

Release Edition
v0.1.5

“Own dogfood, own CI, now with dotfiles.”

Release — v0.1.5
4
PRs Merged
2
Contributors
+152
Lines
Top Stories
  • 1Custom publication titles supported via .gitpulse.jsonDevelopers can now set custom publication titles and move per-project settings into a committed .gitpulse.json file instead of managing them through environment variables.Feature
  • 2GitHub Actions CI unblocked with global CLI installDeployments can now run reliably on GitHub Actions. The fix swaps a broken npx invocation for a global npm install that works on Linux runners.Fix
  • 3Gitpulse CLI bumped to version 0.1.5Version 0.1.5 of the Gitpulse CLI has been released, including support for a .gitpulse.json config file that lets users set custom publication titles and subtitles.
Read the Full Edition→4 stories inside
New Feature·Merged May 7, 2026·M

Custom publication titles supported via .gitpulse.json

#41·by @znat

Developers can now set custom publication titles and move per-project settings into a committed .gitpulse.json file instead of managing them through environment variables.

Monday, May 4, 2026

Release Edition
v0.1.4

“The CLI now asks your hosting provider where it lives. We didn't teach it manners.”

Release — v0.1.4
4
PRs Merged
2
Contributors
+475
Lines
Top Stories
  • 1Site URL auto-detected from Vercel, Netlify, Cloudflare PagesDeploying gitpulse no longer requires setting GITPULSE_SITE_URL manually — the CLI now detects your site URL automatically from Vercel, Netlify, and Cloudflare Pages environment variables at build time.Feature
  • 2Deployment workflows fixed with correct npx syntaxGitHub Actions workflows and documentation examples now use the correct explicit npx invocation, fixing deployments that were silently failing with "command not found" errors.Fix
  • 3GitPulse CLI 0.1.4 releasedVersion 0.1.4 of GitPulse CLI is now available, capturing internal tooling improvements including dogfooded CLI usage, Vercel deployment config, and an updated README.
Read the Full Edition→4 stories inside
Release Edition
v0.1.2

“"We fixed the package.json math. One package gets published, not two."”

Release — v0.1.2
2
PRs Merged
2
Contributors
+75
Lines
Top Stories
  • 1Release automation unblocked after tag collision fixRelease-please was managing two packages and colliding on git tags whenever versions diverged — five PRs failed to publish. The root package is private, never published to npm, and shouldn't have been in the release pipeline at all.
  • 2GitPulse 0.1.2 unblocks release pipelineGitPulse 0.1.2 drops a problematic plugin and fixes documentation alignment to get the automated release workflow moving again.
Read the Full Edition→2 stories inside
Release Edition
v0.1.3

“We taught an LLM to read git diffs and write better than half of us.”

Release — v0.1.3
3
PRs Merged
2
Contributors
+110
Lines
Top Stories
  • 1GitPulse v0.1.3 released with LLM story pipelineVersion 0.1.3 brings a complete local git → LLM → story pipeline, full editorial site redesign, new CLI package, and 12 bug fixes including reasoning block handling and SEO improvements.
  • 2Release plugin removed, pipeline unblockedMonorepo releases should flow freely again after removing a plugin that was blocking version bumps when only one package had changes.Fix
  • 3gitpulse v0.1.2 released with release-please fixVersion 0.1.2 is out, bundling a fix for Release Please so it works correctly in monorepos where linked-versions isn't available.
Read the Full Edition→3 stories inside
Release Edition
v0.1.1

“The CLI shipped. Your analytics now deploy themselves.”

Release — v0.1.1
7
PRs Merged
2
Contributors
+4.8k
Lines
Top Stories
  • 1PR detail page redesigned with tabs and diff viewerThe gitpulse PR detail page now shows richer metadata up front—merged status, size assessment, and category breakdown—before the headline. Story and technical content live in separate tabs, with code blocks rendering line numbers and diffs getting green/red coloring.Feature
  • 2PR details open in slide-in drawer with scroll preservedClicking any feed item now slides PR or commit details in from the right instead of navigating away. The feed stays frozen at its scroll position, and closing the drawer returns users exactly where they were. The panel is deep-linkable via URL.Feature
  • 3Gitpulse CLI shipped to npm with reusable Pages workflowA new CLI package lets any project publish its gitpulse analytics to GitHub Pages, Vercel, Netlify, or custom infrastructure — no bundler or token management required.Feature
Read the Full Edition→7 stories inside
New Feature·Merged May 4, 2026·M

Site URL auto-detected from Vercel, Netlify, Cloudflare Pages

#35·by @znat

Deploying gitpulse no longer requires setting GITPULSE_SITE_URL manually — the CLI now detects your site URL automatically from Vercel, Netlify, and Cloudflare Pages environment variables at build time.

Fixes & Patches

Sunday, May 3, 2026

New Feature·Merged May 2, 2026·XL

PR details open in slide-in drawer with scroll preserved

#25·by @znat

Clicking any feed item now slides PR or commit details in from the right instead of navigating away. The feed stays frozen at its scroll position, and closing the drawer returns users exactly where they were. The panel is deep-linkable via URL.

Saturday, May 2, 2026

Release Edition
v0.1.0

“The newspaper that covers its own commits shipped. We are not handling this well.”

Release — v0.1.0
18
PRs Merged
3
Contributors
+5.1k
Lines
Top Stories
  • 1Release editions surface on homepage feed and /releases/ pagesGitHub releases are now displayed as Special Edition cards on the homepage feed — grouped by publish date and positioned above PR features — with dedicated /releases/ list and detail pages including auto-generated Open Graph images and SEO structured data.Feature
  • 2gitpulse gains install guide, test suite, and story schema validationgitpulse now ships with a proper install guide, 53 passing tests, and a schema contract that catches malformed stories before they reach production.
  • 3Release changelogs now generate automaticallyGitPulse now processes GitHub releases end-to-end, automatically matching each release to its PRs and generating editorial-quality release notes — no manual work required.Feature
Read the Full Edition→18 stories inside
New Feature·Merged May 2, 2026·XL

PR detail page redesigned with tabs and diff viewer

#24·by @znat

The gitpulse PR detail page now shows richer metadata up front—merged status, size assessment, and category breakdown—before the headline. Story and technical content live in separate tabs, with code blocks rendering line numbers and diffs getting green/red coloring.

New Feature·Merged May 2, 2026·M

Releases automated via conventional commit titles

#11·by @znat

Maintainers no longer manually type version numbers. A bot now reads conventional commit titles, computes the bump, and opens a release PR for review—CHANGELOG included.

New Feature·Merged May 2, 2026·XL

Release editions surface on homepage feed and /releases/ pages

#7·by @znat

GitHub releases are now displayed as Special Edition cards on the homepage feed — grouped by publish date and positioned above PR features — with dedicated /releases/ list and detail pages including auto-generated Open Graph images and SEO structured data.

New Feature·Merged May 2, 2026·L

Release changelogs now generate automatically

#6·by @znat

GitPulse now processes GitHub releases end-to-end, automatically matching each release to its PRs and generating editorial-quality release notes — no manual work required.

New Feature·Merged May 2, 2026·M

Release tracking schemas and storage layer landed

#5·by @znat

GitPulse now stores release data alongside stories. Every GitHub release gets its own validated JSON file with denormalized top stories and an inputsHash for skipping redundant AI calls.

Fixes & Patches

Friday, May 1, 2026

New Feature·Pushed May 1, 2026·S

Story URLs now include keyword-rich slugs

d5e91cd·by @znat

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.

New Feature·Pushed May 1, 2026·L

Gitpulse site SEO infrastructure added

c8a2fe2·by @znat

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.

New Feature·Pushed May 1, 2026·S

Author bylines switched to plain @mentions

2a3ee86·by @znat

Story pages now display author names as plain @mentions instead of clickable links, standardizing how attribution appears across the site.

New Feature·Pushed May 1, 2026·M

Gitpulse logo gains brand mark, theme toggle arrives

6012e79·by @znat

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.

New Feature·Pushed May 1, 2026·M

Gitpulse adds incremental daily run processing

3de6587·by @znat

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.

New Feature·Pushed May 1, 2026·L

Gitpulse commit feed redesigned as editorial publication

640c870·by @znat

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.

New Feature·Pushed May 1, 2026·M

Commit analysis parallelized with configurable concurrency

5a51361·by @znat

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.

New Feature·Pushed May 1, 2026·M

PR detector and size assessment added to GitHub analyzer

1815780·by @znat

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.

New Feature·Pushed May 1, 2026·M

Git history now generates editorial stories via LLM

85cefa5·by @znat

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.

New Feature·Pushed May 1, 2026·M

Content collection infrastructure enables story rendering

fbbe018·by @znat

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.

Fixes & Patches