Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Changelog #28

Closed
robwise opened this issue Jan 18, 2017 · 4 comments
Closed

Changelog #28

robwise opened this issue Jan 18, 2017 · 4 comments

Comments

@robwise
Copy link
Collaborator

robwise commented Jan 18, 2017

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.

@jlongster
Copy link
Member

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 apm publish just works?

@robwise
Copy link
Collaborator Author

robwise commented Jan 19, 2017

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.

@robwise
Copy link
Collaborator Author

robwise commented Jan 20, 2017

Okay, turns out I can publish, so all set! Sorry about that!

@robwise
Copy link
Collaborator Author

robwise commented Mar 5, 2017

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.

robwise added a commit that referenced this issue Mar 6, 2017
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants