-
-
Notifications
You must be signed in to change notification settings - Fork 95
Changelog #28
Comments
I removed the current one at least. Not sure a small project of this size warrants a full changelog as it's pretty easy to look at the commit history and read the 1-3 commits between versions. But I'll leave that up to you as the maintainer :) I'm happy to add you to the release process btw. Do I just add you as an "owner" to the npm project and |
Actually, I never actually checked, I was just assuming. Maybe I already am able to by nature of being a GitHub collaborator? Next time that Prettier gets bumped, I will try and see if I can do it. |
Okay, turns out I can publish, so all set! Sorry about that! |
After merging prettier-eslint we're adopting the commitizen + cz-conventional-changelog we should be able to auto-generate one. I just need to figure it out. |
Add an auto-generated changelog using the conventional-changelog CLI. The command that was run is `conventional-changelog -p angular -i CHANGELOG.md -s -r 0`. Closes #28
As per #25 (comment), we should probably blow away the current changelog and then create a new one from scratch that gets us back up to date.
The text was updated successfully, but these errors were encountered: