Sign in Start free
  • AI-Agent
  • Ready to Run

Update GitHub Changelog

Turn merged pull requests into changelog entries and publish releases

Use this Agent instantly or customize it - no programming needed

Add a merged change to Unreleased
Reads
  • Merged pull request
    Merged pull request

    Your merged pull request gives the Agent its summary, labels, and link.

  • Changelog file
    Changelog file

    Your current changelog shows what is under Unreleased and which versions already have sections.

  • Change categories
    Change categories

    You choose which labels or change prefixes mean features, fixes, or internal work.

Code repository
Code repository

Your code repository supplies merged pull requests and keeps the changelog the Agent updates.
Code repository
Is the changelog file or Unreleased heading missing?YesNo
Report the missing changelog setup
Is this change internal-only or already covered?YesNo
Record why this merge needs no new entry
Writes
  • Skip reason
    Skip reason

    You can see why this merged change needs no new changelog entry.

Is the user-facing change unclear?YesNo
Flag the pull request for maintainer review
Writes
  • Pull request review flag
    Pull request review flag

    Your maintainer can review a merge whose user-facing impact remains unclear.

Add one linked entry under Unreleased
Writes
  • Unreleased changelog entry
    Unreleased changelog entry

    Your changelog gains one reader-facing entry with a link to the merged pull request.

Publish the approved changelog section
Reads
  • Release issue
    Release issue

    Your release issue gives the Agent its approval, version, and assigned maintainer.

  • Changelog file
    Changelog file

    Your current changelog shows what is under Unreleased and which versions already have sections.

  • Publication settings
    Publication settings

    You choose the release branch and time zone for the dated changelog section.

Release issue tracker
Release issue tracker

Your release issue tracker confirms release approval and carries the published link to your maintainer.
Release issue tracker
Code repository
Code repository

Your code repository supplies merged pull requests and keeps the changelog the Agent updates.
Code repository
Does the release issue lack one version or an assignee?YesNo
Report the missing details on the issue
Writes
  • Release details request
    Release details request

    Your release issue shows which version or assignee it needs before publication.

Is this version already published and linked on the issue?YesNo
Keep the existing section and issue comment
Is Unreleased empty and this version unpublished?YesNo
Ask the maintainer whether this release needs a section
Writes
  • Empty release question
    Empty release question

    Your maintainer can decide whether a release with no Unreleased entries needs a section.

Date the section if needed and post its link on the issue
Writes
  • Dated changelog section
    Dated changelog section

    Your approved version gets one dated section while Unreleased stays ready for later changes.

  • Release issue comment
    Release issue comment

    Your assigned maintainer receives a link to the published section on the release issue.

This Agent waits for a pull request to merge, then checks your labels. It updates Unreleased for reader-facing changes. On release approval, it dates the section and posts its link for your maintainer.

Modify Agent

Customize this Agent to fit your needs using natural language.

Start Agent for Free

Enter your email address and we will send you a secure link to continue.

Google Drive
Used as:
Show all Agents working with Google Drive
Airtable
Used as:
Show all Agents working with Airtable
monday.com
Used as:
Show all Agents working with monday.com
Asana
Used as:
Show all Agents working with Asana
ClickUp
Used as:
Show all Agents working with ClickUp
Google Contacts
Used as:
Show all Agents working with Google Contacts
Microsoft SharePoint
Used as:
Show all Agents working with Microsoft SharePoint
GitHub
Used as:
Show all Agents working with GitHub
Podio
Used as:
Show all Agents working with Podio
Kintone
Used as:
Show all Agents working with Kintone

Made for your industry

Update GitHub Changelog is made for businesses in these industries.

Made for your role

Update GitHub Changelog is made for people in these roles.

Made for your department

Update GitHub Changelog is made for people in these departments.

How Update GitHub Changelog works

4 steps, in order, on every run.

  1. Review Merged Pull RequestsRead the merged pull request and your chosen labels. Skip internal changes; flag unclear ones for maintainer review.
  2. Update the Unreleased SectionGroup reader-facing changes as features, fixes, or other updates. Add its linked entry to Unreleased if the changelog does not cover it.
  3. Publish the Dated SectionConfirm the release issue's approval and version. Date the Unreleased entries and leave the heading ready for later merges.
  4. Share the Changelog LinkComment on the release issue with the dated section's link for its assigned maintainer. Reuse an existing link without repeating the comment.

How to Get Started

Connect your tools

Connect the tools you already use, such as Google Drive, Airtable or monday.com.

10 tools
Set your rules
  • Choose the repository, release branch, and path to the changelog file, with an Unreleased heading already present.
  • Choose which pull request labels or conventional change prefixes indicate features, fixes, other user-facing updates, or internal-only work.
  • Choose the release approval issue type and approved status; put the release version on each issue and assign it to the maintainer.
  • Configure the release issue's comment notifications to reach its assignee, and choose the time zone used for the published date.
Launch the Agent

Use safe mode to approve every result before it goes out, or let the Agent run automatically.

FAQs

Frequently asked questions about the Update GitHub Changelog:

Can I use conventional changelog rules?

Yes. You choose which pull request labels or change prefixes mark features, fixes, other updates, and internal work.

What if a merged pull request is unclear?

Your maintainer gets the pull request for review when its summary and labels do not show a reader-facing change. The changelog stays untouched.

What do I need to publish a release?

Your release issue needs an approved status, one version, and an assignee. You choose the date's time zone and enable comment notifications for that assignee.

What happens if Unreleased is empty?

Your changelog stays unchanged. The Agent asks the maintainer whether this release needs a section.

What happens when the Agent is unsure?

It stops and asks you. The Agent does not guess when it reaches a decision you have not approved.

Can I review its work?

Yes. Every run creates a plain-language log that you can review and export. Logs are kept for twelve months.

What happens if I cancel?

The Agent stops at the end of the billing month and its tool connections are removed. Your run logs remain available for twelve months.

Related Agents

Agents related to Update GitHub Changelog

More ready-to-run Agents for connected work.

Send Current Proof

Your reviewer gets the current image or PDF and a clear question. Your review card shows which revision you sent.

Works with19 tools
Published by Creative Review Essentials
Flag Proof Mismatches

Your coordinator gets both revision links in chat when the task and current proof differ, with the task held for a human choice.

Works with17 tools
Published by Creative Review Essentials
Pin Current Proof Versions

Your review card shows the current proof revision and its file link, so makers and reviewers know which version needs attention.

Works with9 tools
Published by Creative Review Essentials
Update Proof Links

Your rework card points to the latest image or PDF proof, with the next reviewer clear when a shared file changes.

Works with9 tools
Published by Creative Review Essentials