Your changelog is always behind
Draft changelog updates from the GitHub issues where the work already happens. Review, approve, and publish with @feedlog publish.
Free to start. Setup in under 5 minutes.
The same work in GitHub—presented the way customers expect.
Before · GitHub issue
we should add a csv export button on the analytics dashboard so i can share reports quickly with clients.
After · Public changelog
Issue
Feedback in GitHub
AI draft
Structured in-thread
Review
You stay in control
Publish
Live for users
Teams ship in GitHub, but user-facing notes lag or get skipped. FeedLog drafts updates from issue threads so “what changed?” stops turning into repeat support pings.
Release communication is high-trust content. Our bot drafts in the issue thread; nothing is public until you say so — not autopublish by default.
Publish when it’s ready: your embedded changelog updates for users as soon as you approve. Optional upvotes show what resonates — GitHub stays the source of truth.
Install FeedLog and pick repositories.
Generate an API key in dashboard installation settings.
Paste one component or script on your site to show changelog updates.
Watch how a messy GitHub issue becomes a clear changelog entry, in seconds, without leaving your repo.
It starts with a regular GitHub issue in your repo. You describe the request in your own words.
we should add a csv export button on the analytics dashboard so i can share reports quickly with clients.
Our bot picks up the issue, analyzes the content, and prepares it for improvement.
📋 Draft · Retries Left: 3
| # | Body | ✓ |
|---|---|---|
| 1 | we should add a csv export button on the... | ✅ |
Our AI rewrites the issue to be professional, clear, and structured so it is ready to share as a product update.
Teams need to share analytics with stakeholders who do not have dashboard access, without granting full product accounts.
Adds a CSV download for the metrics currently visible in the analytics dashboard for a selected date range.
.csv file downloads with the columns shown in the tableReview the draft, then comment @feedlog publish — nothing is public in your changelog until you do.
✅ Published · Retries Left: 3
| # | Body | ✓ |
|---|---|---|
| 1 | we should add a csv export button on the... | |
| 2 | ## Motivation Teams need to share analytics... | ✅ |
@feedlog publish
✅ Issue published successfully
The issue instantly appears in your changelog widget, ready for your users to view and optionally upvote (signal on published work — not a full feedback board).
Want the changelog to show that work is underway?
Assign someone to the issue on GitHub. FeedLog uses assignees to mark the entry In progress in your public widget.
Control your changelog directly from GitHub comments using these powerful commands.
@feedlog publishPublishes the issue to the public changelog
@feedlog publish
✅ Issue published successfully
@feedlog unpublishRemoves from public changelog
@feedlog unpublish
✅ Issue unpublished successfully
@feedlog retryRegenerates AI content (uses 1 retry)
@feedlog retry
✅ Retry initiated. 2 retries remaining.
@feedlog switch <number>Switches to a specific revision
@feedlog switch 1
✅ Switched to revision: 1
@feedlog show <number>Displays full revision content
@feedlog show 2
The application unexpectedly terminates...
@feedlog revertReverts to the previous revision
@feedlog revert
✅ Reverted to revision: 1
Connect your repo, set your AI instructions, review drafts in issues, and ship your first public update with @feedlog publish, usually in under five minutes. Free to start.