Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It always depends on your users. Such a changelog is suitable for stuff other developers use, but not for end users.

But it is a _way_ better starting point to write a changelog that 'usual' commit messages or PR descriptions.



I disagree. I publish to the end users and they are grateful all the time.

I use custom scheme tho, using Gitlab issue title and issue labels. I find this more meaningful since one issue can contain multiple PRs and I still want single changelog line.


How can I, as a user, know if bug x, or issue y is resolved, without a changelog?!


Nobody suggested not having a changelog.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: