Pull request digest

Turn a list of pull requests into a readable change overview.

Prompt 106 words

Summarize the supplied pull requests in two Markdown sections.

SUMMARY: Write one sentence describing the main themes across the pull requests.

TOP PULL REQUESTS: Use a short bulleted list for the most important changes. Rewrite unclear titles in plain language that describes the proposed behavior. Group closely related work when doing so improves readability.

Preserve pull request numbers, links, and status when supplied. Distinguish proposed, open, and merged work; do not describe a proposal as shipped. Explain why a change matters only when the input supports that explanation. Skip duplicate titles and low-value wording changes unless those changes are the main subject. Return only the digest.

Example

Weekly activity in an illustrative notes repository

Before 92 words

This week's Note Desk work includes PR #71, "restore labels", which is merged. It fixes labels disappearing when an archived note is restored. PR #72, "csv howto", is also merged and documents CSV export for workspace administrators; it does not change export permissions. PR #73, "offline shared", remains open. It proposes offline edits to shared notes, with conflicting edits shown for review when users reconnect. That behavior is not yet merged or released. The activity feed lists #71 twice because the author renamed its title; both entries refer to the same change.

After 51 words

SUMMARY Note Desk merged a restore fix and export documentation; offline shared-note editing remains proposed. TOP PULL REQUESTS - #71, merged: Preserve labels when archived notes are restored. - #72, merged: Document administrator CSV export; permissions unchanged. - #73, open: Propose offline shared-note edits with conflict review on reconnect; not released.

Examples illustrate the method. They do not measure model output.

Files and sources

Adapted from Fabric · summarize_pull-requests. Source notes.