Snippet
const title = commit.subject.replace(/^w+([^)]*):s*/, '');Loading content
Patchweek
Clear weekly release notes from the commits you already ship.
- 5 milestones
- 5+ updates
- since 2026
Clear weekly release notes from the commits you already ship.
The milestones that explain how the project has evolved.
The project started with a simple need: Clear weekly release notes from the commits you already ship.
The first build kept Patchweek focused on one useful workflow before adding broader tooling.
The GitHub import is useful when it works; the rough edge is explaining what got skipped. Patchweek now lists every skipped change instead of silently hiding it.
A small beta covered the core review flow. The integrations still needed more maintenance than the teams' willingness to pay could support.
The release flow worked for a few teams, but every integration needed ongoing care and the paid demand never caught up with that work. I am closing the project and keeping the best parts of the review flow for another product.
Public updates from the builder about this project.
const title = commit.subject.replace(/^w+([^)]*):s*/, '');Had a lovely call with a team using the weekly email as their release meeting agenda. That is a better use case than my homepage copy.
one command + an error message that says what to do. support inbox went quiet in like an hour. shoulda done this ages ago.
A little bug in the timezone preview made Sunday look like Monday. Fixed, and I owe the calendar app an apology.
i like building in public, but i also like my customers trusting me lol. wrote down the line i try not to cross when sharing progress
Help Patchweek learn from real people.
After reviewing one release, what would make Patchweek valuable enough to keep in your team's workflow?
Sign in to respond to this request.
Conversation
Share an idea, a question, or a useful experience.
Sign in to comment.
No comments yet