GitHub Integration
KittyLog connects through the GitHub App install flow — no tokens to manage or webhooks to configure manually. Everything is set up automatically when you connect a repository.
Webhook Events
KittyLog registers webhooks to listen for the events that trigger changelog generation:
create— new git tags (Tag mode)push— new commits (Scheduled mode uses this to know when there's something to summarize)
Hosted Changelog Page
Every connected repo gets a hosted changelog at kittylog.app/c/owner/repo. Enable Hosted URL visibility in Sharing to make it public, then share the link or add a README badge. On the Business plan, readers can translate any changelog into one of 16 supported languages on-demand. You can also point a custom domain at it (see Custom Domains).
CHANGELOG.md Sync
Every plan can keep release notes in the repository through a pull request. Open your repository's Overview tab and find CHANGELOG.md sync. Choose Create CHANGELOG PR to export published entries, or Regenerate CHANGELOG PR if you closed a previous PR without merging.
Turn on Auto-create PR after generation to create or update a PR automatically. Automatic sync can include a generated draft while it remains unpublished on KittyLog. Review and merge the PR through your normal GitHub process.
The GitHub App needs permission to write repository contents and pull requests. If GitHub asks you to approve updated app permissions, approve them before retrying the sync.
Permissions
KittyLog requests the minimum permissions needed:
- Code & commits (read) — to analyze changes
- Metadata & releases (read) — to detect events
- Contents (write) — needed to create the branch and commit for a
CHANGELOG.mdpull request or to publish generated notes to GitHub Releases - Pull requests (write) — needed to open or update CHANGELOG.md pull requests