Custom publication titles arrive in Gitpulse
Gitpulse now reads a .gitpulse.json file at the repo root, letting maintainers set custom publication titles and subtitles alongside per-project analysis preferences.
Gitpulse publications can now have custom titles and subtitles without touching source code. Maintainers drop a .gitpulse.json file at the repo root to set publication preferences, adjust how analysis runs, and tune dispatch titles — all in one place. Your newsletter header just became your problem, not the CI's.
CI deployments work reliably on Linux now. The gitpulse CLI installs globally instead of relying on npx, which was hitting a PATH resolution bug on Linux runners while macOS sailed through unaffected. If your pipeline runs on multiple operating systems, you can finally trust it.
The self-deploy workflow has been un-stuck. It now tracks @main for the publish-pages action instead of a broken pinned version, meaning gitpulse's own CI should go green and fixes can ship immediately without waiting for a formal release. The projectdog is eating its own dog food, and the bowl is clean.
Gitpulse now reads a .gitpulse.json file at the repo root, letting maintainers set custom publication titles and subtitles alongside per-project analysis preferences.
GitHub Actions deployment workflows now work reliably — the gitpulse CLI installs globally instead of relying on npx, which was hitting a PATH resolution bug on Linux runners.
Gitpulse CLI ships with a new .gitpulse.json configuration file, letting users customize how their publication appears.