Skip to content

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

Works with GitHub, GitLab and Bitbucket. No code changes.

Every merge leaves a note. You decide which ones the world reads.

1. Merge

You merge a pull request as usual. Petek reads its title, description and labels.

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.

3. Approve

Someone edits, approves or leaves it out. Nothing goes public until a person presses Approve.

1.0 The queue

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.

2.0 Publish day

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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 plans

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.

Start with your next merge.

Start a workspaceTalk to us

Free for one workspace.