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 dispatches now carry custom branding. A new .gitpulse.json config file at the repo root lets maintainers set publicationTitle and publicationSubtitle — fields that previously fell back to auto-generated defaults like "The Gitpulse Conversation". The file also absorbs four settings that previously lived in environment variables: bootstrapDays, concurrency, releasesCap, and includePrereleases. These are per-project preferences rather than deployment secrets, so they belong in committed config alongside the display settings.
The change splits configuration into two concerns: environment variables handle secrets and platform-specific settings, while .gitpulse.json handles project preferences. Validation errors now name the offending field, making misconfigured files actionable for users. In the gitpulse CLI, a new project-config module reads the file at startup; in the generated site, publicationName() and publicationSubtitle() check the config before falling back to defaults.