How it works
Connect a repository, pick a branch, choose who approves.
No code changes. Four steps, and from the next merge on, every merge has a note.
1.0
Connect a repository and pick a branch.
Sign in with GitHub, GitLab or Bitbucket and choose the branch you ship from. Petek asks only to read pull requests; it never asks to write.
Connect a repositoryRead-only
- GitHubconnected
- GitLab
- Bitbucket
Repositorypetek/web
Branch you ship frommain
2.0
Choose who approves, and your day.
One approver or a few, per repository. Tuesday is the default publishing day; any day works, or publish right after each approval.
Who approvespetek/web
mayatom+ Add
Publish day
SunMonTueWedThuFriSat
Or publish right after each approval
3.0
Each merge becomes a draft.
Within minutes of a merge, a draft waits in the queue: a title, two or three lines, and the pull request it came from. Edit it like any text.
Draft · from #482 · 4 min ago
Notes in two languages
Each draft can now come in English and Hebrew side by side.
4.0
Approve, and the changelog updates itself.
On your day, everything approved goes out together: on your changelog page, by e-mail to subscribers and in the RSS feed.
changelog.petek.example
Changelog
- 10 Nov 2026Notes in two languages
- 10 Nov 2026Preview a note in your colours
- 3 Nov 2026Leave it out with one key
What Petek never does
- It never publishes a note no one approved.
- It never writes to your repository.
- It never reads your source code: only the pull request's title, description, labels and file names.
- It never sends a note to your customers by itself, on any channel.