Shiplog after 30 days: everything I've learned about changelogs no one ever reads

Last month I released Shiplog, a simple service that generates a changelog page out of merged pull requests. The reason why I made it was that I kept forgetting to write down release notes for my personal projects and the users were asking me what had changed.

Here is what I have learned from the first 30 days of using Shiplog. People generally do not read changelogs, but those who do, are your best clients. Two of the first users told me that they look at the page before making the decision to renew their subscription. Another thing is that automatically generated notes sound like written by a robot, so I added a possibility to edit them before publishing.

What I haven't been able to figure out is how to distribute this. Developers love it, but I have trouble reaching the founders that would be helped by this and who aren't on GitHub. Any suggestions are appreciated, and I am happy to explain my system further.

If you keep a changelog, what exactly do you put in it and who do you expect to read it? I'm not here to sell, just looking to get this right. If you prefer testing it out, I'm all ears as to what is wrong with it.