A note for every merge.
Petek drafts a release note from each merged pull request. Someone on your team edits it and presses Approve, and only then does your public changelog update.
New: Notes in two languages
- Add Hebrew drafts beside English#482 · maya · 4m
- Fix date order in RTL changelog#479 · tom · 1h
- Bump eslint to 9.14#477 · deps-bot · 3h · left out
- Keep scroll position in the queue#474 · dana · 5h
- Preview a note in your colours#471 · maya · Mon
#482 Add Hebrew drafts beside English merged into main by @maya
Draft · from #482
Notes in two languages
Each draft can now come in English and Hebrew side by side. Edit either one; approving the note approves both.
Leave out EEditApprove A
Works with GitHub, GitLab and Bitbucket. No code changes.
Every merge leaves a note. You decide which ones the world reads.
Merged #482 into main
Add Hebrew drafts beside English
maya merged 3 commits · 4 minutes ago
editor/rtl.tsnotes/draft.ts+2
1. Merge
You merge a pull request as usual. Petek reads its title, description and labels.
Draft · from #482 · 4 min ago
Notes in two languages
Each draft can now come in English and Hebrew side by side.
2. Note
Within minutes a draft waits in your queue, written for the people who use your product, not for the people who wrote it.
Notes in two languages
Waiting for approval · publishes Tuesday
Leave outEditApprove
Last week: 6 approved, 2 left out
3. Approve
Someone edits, approves or leaves it out. Nothing goes public until a person presses Approve.
One queue for every note.
Every draft lands in the same place, in the order it was merged. Read it, change a word, approve it. Or leave it out: a version bump doesn't need a note.
One repository, one approver: you. The queue fills while you review code, and the changelog writes itself from what you approve.
- Parse leap years before 1900#311 · lior · 12m
- Bump dev dependencies#309 · deps-bot · 2h · left out
- Add a format() for durations#306 · you · Sun
#311 Parse leap years before 1900 merged into main by @lior
Draft · from #311
Leap years before 1900
parse() now reads 29 February correctly for years before 1900. Nothing to change in your code.
Leave out EEditApprove A
Engineers merge, the product manager approves. Each note says what changed for the customer, in your team's words.
- Split invoices by project#1288 · eli · 20m
- Refactor PDF renderer#1285 · ruth · 2h · left out
- Show VAT per line#1281 · eli · Mon
#1288 Split invoices by project merged into release by @eli
Draft · from #1288
Split an invoice by project
You can now split one invoice into several projects before you send it. Each project keeps its own total.
Leave out EEditApprove A
Support sees every note before it goes out, and knows what changed before the first customer asks.
- Show VAT per line#1281 · eli · Mon · seen
- Faster search in clients#1279 · ruth · Mon · seen
- Export to CSV keeps filters#1276 · noa · Sun
#1281 Show VAT per line merged into release by @eli
Draft · from #1281
VAT on every line
Each line of an invoice now shows its own VAT, and the total adds them up. Older invoices are unchanged.
Leave out EEditApproved ✓
Merge on Tuesday. Read it on Tuesday.
Merge on Tuesday, and the note is in your queue on Tuesday. Nothing goes public until someone presses Approve. On your publishing day the changelog updates itself with whatever was approved that week.
This weekPublish day: Tuesday
- Sun82 merged
- Mon93 approved
- Tue10Publish day
- Wed11
- Thu12
- Fri13
- Sat14
- Notes in two languagesapproved
- Preview a note in your coloursapproved
- Keep scroll position in the queueapproved
- Bump eslint to 9.14left out
Changelog
Full changelog- Notes in two languagesEach draft can now come in English and Hebrew side by side. Edit either one; approving the note approves both, and each language gets its own changelog page.
- Leave it out with one keyPress E on a draft to leave it out of the changelog. It stays in the "Left out" list, so you can bring it back before publish day.
- A Slack line when a draft waitsChoose a channel, and Petek posts one line when a draft waits for its approver. Nothing else; no summaries.
- Your changelog on your own domainPoint a subdomain such as changelog.your-product.com at Petek; the page follows your colours and your logo.
Pricing, by who you are.
Compare plansOne maintainer
For an open-source project or a side product.
Free for good, for one workspace
Start a workspace- One workspace, one repository
- One approver: you
- A public changelog on a petek page
- Publishing on Tuesdays
A product team
For a team that ships every week.
$8 per approver, a month. Writers and readers are free
Start a workspace- Up to 10 repositories
- Any approvers, any publishing day
- The changelog on your own domain
- A Slack line when a draft waits
- Notes in two languages
A company with several products
For several products, each with its own changelog.
From $240 a month, billed yearly
Talk to us- A changelog for each product
- Approval rules per product
- Single sign-on
- An invoice in dollars or shekels
Questions
Does Petek publish anything by itself?
No. A note goes public only after a person presses Approve.
What does Petek read?
The merged pull request's title, description, labels and the names of the changed files. Never your source code.
Do we need to change our code or our CI?
No. You connect the repository from Petek's settings; nothing in the repository changes.
Can we publish on another day?
Yes: any day, or right after each approval. Tuesday is only the default.
Can the changelog be in Hebrew?
Yes: English, Hebrew or both, right to left where it should be.
When can we reach you?
Sunday to Thursday, 09:00–18:00 Israel time, at hello@petek.example or from the chat in the product.