Changelog Modes
Choose generation timing separately from commit grouping and publishing. Automatic timing generates on a schedule or a Git tag push. Manual timing waits for your generation request while keeping your chosen grouping. Change timing in the repository's Overview tab.
Scheduled
RecommendedAutomatically generate a changelog on a daily, weekly, or monthly schedule summarizing all changes since the last generation.
Runs on your chosen schedule - Only generates if new commits exist
On Git Tag Push
Generate a changelog whenever you push a new Git tag. Perfect for projects with versioned releases.
Triggered by: Git tag push (e.g., v1.0.0, release-2024-01)
Generate Manually
- Open Overview → Generation → Generation timing and choose Manual. This setting is available after connecting. New repositories start in Automatic, so initial backfill may already have started. Queued automatic work is skipped; generation already underway may finish.
- Keep your desired grouping: Daily, Weekly, Monthly, or By Git Tag. When pending items are available, choose Generate N pending changelogs in Generation timing. The button is disabled when there are no pending items or generation is in progress.
- Watch the generation progress, then open Changelogs to inspect the resulting entries. Manual timing does not change Manual approval, Publish after 24 hours, or Publish immediately. Choose Manual approval if you want to review drafts before publication.
The progress banner shows Generating changelogs and a queued count; a completion banner reports the generated count. A skipped item may produce no entry: the result can say No changelogs generated and show a skip reason. Nothing relevant to announce is a successful skip, not a published update. Queue or generation failures show an error; use the troubleshooting steps below rather than assuming completion means every item produced a changelog.
To return to Automatic, first check the acknowledgement that changes accumulated during Manual mode can be generated through backlog discovery, scheduled runs or retries, then select Automatic. Review your publishing policy and GitHub delivery settings before doing so.
Writing Style Presets
Control the tone, detail level, and formatting of your changelogs. These settings are configured per-repository so each project can have its own voice.
Preset
Users — focused on features, improvements, and fixes your customers can use or notice. Internal maintenance is left out. Developers — includes technical context like affected modules and APIs. Custom — write your own system prompt for full control over output.
If there is nothing relevant to announce for your audience, KittyLog skips the entry. Nothing is published or sent to subscribers. Regenerating an existing entry keeps its current content when there is nothing relevant to announce.
Technical Language
Plain, Balanced, or Technical. Controls how much jargon and implementation detail appears.
Verbosity
Brief, Normal, or Detailed. Determines how much each change is elaborated on.
Emoji Use
Off, Subtle, or Expressive. Adds visual markers to category headings and list items.
Category Style
Friendly (What's New, Improvements, Bug Fixes) or Technical (Added, Changed, Fixed, Security).
Advanced Options
Fine-tune what context the AI uses when generating changelogs. These options are available on Pro plans and above.
Include Code Diffs
Pass git diffs to the AI for richer, more accurate summaries. May increase generation time.
Include PRs & Issues
Pull in PR descriptions and linked issues for additional context. Useful for repos with detailed PR workflows.
To control when entries go live, see Review & Publishing. Publishing controls are available on every plan.
No New Changelog?
- In Overview → Generation → Generation timing, check whether Manual is selected. In Manual, choose Generate N pending changelogs when available; scheduled runs and tag pushes do not start generation. Skipped items can have no relevant changes to announce; inspect the displayed result before retrying.
- For scheduled generation with Automatic timing, check the selected frequency, time, and timezone. A scheduled run needs new commits to summarize.
- For tag mode, push the tag to GitHub and check your ignore patterns. A matching tag is skipped.
- Check the Changelogs tab, including its draft and date filters. Changing modes can hide entries from another mode; a generated draft also stays off the public page.
- If generation reports an error, check that the GitHub App still has repository access. If it persists, contact support with the repository name and the displayed error.