At a glance
Drafts changelog, blog, and social copy from GitHub commits and merged pull requests. Source receipts stay beside new drafts; publishing the changelog is a separate action.
Vision
Developers ship fast but lag on communicating what they shipped. GitHerald reads GitHub commits and merged PRs for a selected UTC date range and generates changelog, blog, and social drafts. The signed-in dashboard retains source identities, with verified links when available, for new drafts so users can inspect the underlying work. The reader pages through GitHub activity and refuses a partial draft when its 1,000-record scan limit or a provider page failure prevents a complete result.
The public GitHerald overview explains this source-run workflow. It is a static product page, not a hosted GitHub connection, AI generation service, account, or published changelog instance.
The Problem
Communication debt is real. Writing changelogs is tedious, blog posts about releases rarely happen, and social media is an afterthought. Existing tools are fragmented — git-cliff for changelogs, Typefully for social scheduling, Beamer for widgets. No tool bridges the full pipeline.
Key Differentiators
- GitHub context: Sends commit messages and merged PR descriptions to the configured AI provider; new generations retain commit and PR identities, with verified links when available.
- One generation flow: Creates changelog, blog, and social drafts together, with tone presets and export options.
- Changelog publishing: A separate user action publishes a changelog to the configured app's public page. Changelog, blog, and social drafts can be edited and saved together before export or explicit changelog publication. Blog and social outputs remain copy/export drafts; scheduling, direct posting, and brand-voice learning are not implemented. No public hosted signup or pricing is announced here.