
I built a SaaS for 2 years and never wrote a single changelog. So I automated it.
Let me be upfront about something embarrassing. I've been running Geentoo — a platform for connecting project ideas with co-founders and collaborators — for almost two years. Real users, real features shipped, real bugs fixed. And I have never written a changelog. Not once. Not a release note. Not a "what's new" email. Not even a pinned post saying "hey, here's what changed this month." Nothing. Why though? It's not that I don't care about communicating with users. I do. The problem is my git history. Here's a completely honest sample of what it looks like: fix wip test ok now it works PLEASE work final final2 ok this is the real final asdfgh Sound familiar? Every time I thought "I should write a changelog", I'd open the git log, stare at 300+ commits that looked like the above, and immediately feel exhausted. Then I'd close the terminal and go work on something else. The gap between raw git history and readable release notes is enormous. You have to: Filter out the noise (CI runs, ver
Continue reading on Dev.to Webdev
Opens in a new tab



