Weekly Changelog from PRs

Don’t want to set this up manually? Paste a link to this page into a Devin session and ask it to set everything up for you.

Connect Slack

Devin posts the changelog to Slack and opens a PR against your docs repo, so you’ll need the Slack integration connected.Go to Settings > Connections > Slack and connect your workspace. Devin will be able to post messages to any channel it’s invited to. Add Devin to the channel you want changelogs posted in (e.g., #releases). See the Slack integration guide for details.

Create the weekly schedule

Navigate to Schedules in the left sidebar of app.devin.ai, or use the Schedule Devin option in the input box context menu on the home page. Click Create schedule and configure:

Frequency: Weekly — e.g., every Friday at 4:00 PM UTC
Repositories: Select the repos Devin should scan for merged PRs
Slack channel: Select a channel (e.g., #releases) so your team sees the changelog when it’s ready
Prompt: Be specific about repos, grouping logic, tone, and output format — and tell Devin to match the style of existing entries in your changelog so the output is consistent week over week

Devin scans each repo for PRs merged in the past 7 days, reads their titles, descriptions, and labels to categorize them, then generates output like this:

# Changelog — Week of Feb 14, 2026

## New Features
- **User profile avatars** — Upload custom avatars from the settings page (#412, @alice)
- **CSV export for analytics** — Export any dashboard chart as CSV (#398, @bob)

## Bug Fixes
- **Date picker timezone** — Fixed UTC offset in booking flow (#419, @carol)
- **iOS nav overlap** — Resolved navbar covering content on Safari (#421, @dave)

## Improvements
- **API rate limiting** — Per-key rate limits on webhook endpoints (#210, @bob)
- **Search performance** — Full-text search 3x faster on large datasets (#405, @alice)

Tailor it to your audience

The same schedule can produce different outputs depending on who reads the changelog. Add Knowledge entries to teach Devin your team’s conventions, or adjust the prompt for different audiences.For internal engineering teams — include PR numbers, author handles, and links to the PRs. Mention infrastructure changes and internal tooling updates.For user-facing release notes — strip technical details, rewrite in plain language, and skip internal changes entirely: