Notifications

Available on every plan, including Free. Messages go to your GitHub email by default. In Settings → Notifications, set a custom email address, choose an email theme, or pause all email notifications. Use the per-repository email preferences to choose which repositories send new-changelog alerts.

Plus, Pro, and Business let readers subscribe to a public changelog. Share the public page, then readers enter their email in the subscription form and confirm through the email they receive. Readers do not need a KittyLog account.

Confirmed subscribers receive new published updates, including immediate, manual, and 24-hour automatic publication. They can unsubscribe through a link in each email. Drafts are not sent, and editing, regenerating, or republishing an entry does not trigger another reader email. These subscriptions are separate from owner alerts.

Plus, Pro, and Business can post updates to Discord with formatted sections and a link to the full changelog. Open your repository's Notifications tab and paste the channel's webhook URL into the Discord field. Set up a webhook for each repository you want to announce.

Use the inline setup guide to create the webhook. Select Test to check the connection, then Save to connect the channel. Only published changelogs are announced; drafts wait until you publish them.

Send published changelogs to a Slack channel on Plus, Pro, or Business. The first update arrives immediately; updates that follow within five minutes are grouped into a digest.

1. Open your repository's Settings, select Notifications, and choose Add to Slack.
2. Choose your Slack workspace and the channel you want to notify, then approve the connection. Your workspace may require an admin's approval.
3. KittyLog saves the channel and enables delivery. Send a test to check the connection. Use Change Slack channel to choose another destination. Replacing a paused connection keeps it paused.

Existing webhooks keep working. To enter one manually, expand Use an incoming webhook, paste your Slack incoming webhook URL, and select Save webhook. This option also works when Add to Slack is unavailable.

Pause delivery with the Post to Slack toggle or remove the connection from this repository. Removing it does not uninstall the Slack app from your workspace. The Publish All confirmation can skip Slack for a batch.

Each repository has its own email preference and Discord and Slack webhooks. To stop Discord delivery, remove that repository's webhook. Pause Slack with the Post to Slack toggle, or disable email for the repository. An account-wide email opt-out still applies to every repository.

• Owner email:check your address in Settings → Notifications, spam folder, account-wide email opt-out, and the repository's email preference.
• Reader email: confirm the subscriber clicked the email confirmation link and the repository has Plus or higher. Reader mail requires a published entry. Check spam and remember that editing or republishing an entry does not resend its email; see notification timing.
• Discord or Slack:check the repository's webhook, send a test, and save the configuration. Slack also needs Post to Slack enabled. These channels require Plus or higher and a published entry.
• Check whether Discord and Slack were skipped in a Publish All confirmation. Slack updates following the first within five minutes are grouped into a digest, so they may not arrive individually.