Merged PRs to Launch Copy
Turn merged GitHub PRs into source-linked launch copy, a newsletter draft, and social drafts. Verify release and audience availability before calling a feature shipped; publish only to destinations you explicitly approve.
What Okou delivers: the post, the email, and the thread
This is a real Okou product update, published on okou.ai on July 20, 2026, shown exactly as it went out: the blog post, the same update as a newsletter, and as a thread on X. One run wrote all three from the week's merged pull requests.
What is changelog automation?
Changelog automation is the practice of generating your product update from the work your team actually merged, instead of writing it from memory at the end of the week. Turn merged GitHub PRs into source-linked launch copy, a newsletter draft, and social drafts. Verify release and audience availability before calling a feature shipped; publish only to destinations you explicitly approve.
Why the weekly changelog eats a Friday
Friday afternoon. Thirty-something pull requests merged this week and someone has to turn them into an update people will actually read. You skim the merge list, guess which changes are user-facing, write the post, cut it down for the email, cut it down again for X, then paste each version into a different tool. It is the same reading three times over, and the version that lands on X usually says something slightly different from the one that landed in the inbox.
How Okou turns released changes into launch drafts
1. Choose the accounts and access
2. Start in the Okou conversation
3. Review and reuse the workflow
GitHub, Resend, X, and Slack integrations for changelog automation
GitHub supplies change and release evidence. Resend, X, and Slack are optional destinations with separate access and delivery instructions. The starter returns drafts in the conversation.
GitHub integration: what Okou reads to build the changelog
RequiredOkou reads PR details and checks available release, deployment, and feature-availability evidence. Labels and changed paths help find candidate updates, but a merge alone does not establish that customers can use the feature. Missing release evidence is marked before customer copy is prepared.
Resend integration: the approved newsletter campaign
OptionalResend is optional for a newsletter you approve. Confirm the exact campaign, sender, audience, and content before sending. Okou reports the returned send state and any later delivery evidence separately; an accepted send request is not a delivered message count.
X integration: social drafts and approved posts
OptionalOkou prepares copy for X with the intended account and links. Publication is a separate explicit action after review. A thread’s confirmed post links and any partial failure are reported without blindly reposting uncertain entries.
Slack integration: where the draft waits for approval
OptionalKeep the draft in Okou or explicitly request delivery to a named Slack channel or thread. Feedback can inform a revision, while publication still requires authorization from the user for the final destination and content.
Okou vs. writing it by hand vs. a changelog generator
Changelog automation splits into two problems: deciding what is worth announcing, and getting the announcement to every channel. Most tools solve one of them.
Writing it by hand
Someone reads the merge list, decides what matters, writes the post, and rewrites it twice for email and X. The judgement is good and the copy is on-brand, but it costs the same 90 minutes every week and it is the first thing dropped in a busy week.
A changelog generator
Commit or pull request titles are collected into a release-notes page automatically. It never misses a merge, but it publishes titles rather than themes, cannot tell a refactor from a feature, and stops at one destination.
Okou's changelog workflow
Okou checks what is available to customers, groups the changes into useful themes, and prepares distinct newsletter, blog, and social drafts. Publishing uses the final content, account, audience, and scope you approve, with a verified status for each destination.
Tips for better results
Frequently asked questions
How do merged PRs become launch copy?
Okou reads the changes, checks available release and audience evidence, and groups verified customer-facing behavior into a product update, newsletter, and social drafts.
Does a merged PR mean the feature is live?
No. Release, deployment, and feature-switch availability must be checked separately. Unverified or internal-only behavior is excluded from a customer launch or explicitly marked as not yet available.
Will the workflow publish automatically?
The starter prepares drafts only. Review the exact copy, destination account, and audience before authorizing a CMS publication, Resend campaign, or X post.
Can this run on a schedule?
Yes. Save the reviewed instructions as a workflow and configure a schedule or a supported GitHub event. Connecting the repository alone does not create a trigger.
Publish this week's changelog
Start in the Okou conversation with your sources and the result you need. Review the first result, then decide which parts to save as a workflow.
