Across all the organisation some changelogs are missing dates, links, etc. They should all look like this: https://github.com/pestphp/pest/blob/master/CHANGELOG.md.
I highly suggest looking into https://github.com/symplify/changelog-linker. I have started using it on all my older and new projects and its very clean and easy to you.
Example output: https://github.com/HDInnovations/UNIT3D-Community-Edition/blob/master/CHANGELOG.md
@nunomaduro
How do you think?
Is it right to use changelog-linker in terms of keep a changelog?
I think manual writing is the best way for users of the package.
Another option is to use the "changelog-linker" output to make manual adjustments (or fill partially) to the "changelog.md".
For now, I prefer to do it manually.
What we really need is:
I'll apply these changes to any of the repos I help maintain tomorrow. 馃憤
plugin](https://github.com/pestphp/pest-plugin/blob/master/CHANGELOG.md)plugin-coverage](https://github.com/pestphp/pest-plugin-coverage/blob/master/CHANGELOG.md)plugin-faker](https://github.com/pestphp/pest-plugin-faker/blob/master/CHANGELOG.md)plugin-init](https://github.com/pestphp/pest-plugin-init/blob/master/CHANGELOG.md)plugin-laravel](https://github.com/pestphp/pest-plugin-laravel/blob/master/CHANGELOG.md)plugin-livewire](https://github.com/pestphp/pest-plugin-livewire/blob/master/CHANGELOG.md)They seem to be normalised now.
Most helpful comment
I highly suggest looking into https://github.com/symplify/changelog-linker. I have started using it on all my older and new projects and its very clean and easy to you.
Example output: https://github.com/HDInnovations/UNIT3D-Community-Edition/blob/master/CHANGELOG.md