-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a changelog #20
Comments
@nikitavoloboev Are we ready for a version 1.0.0 release ... there is still some open issues, but I feel like we have a core product down Plus, the command line tool already says that we're on version 1.0.0 |
Agreed, let's release |
I am not sure the process of releases is, I think pushing code to github is currently the way people do that. Then |
I agree ... the Git tag will probably have to come first (which I don't think I'll be able to do) nikitavoloboev/markdown-parser#14 (comment) |
I made a tag & pushed it https://github.com/nikitavoloboev/license-up/releases Not sure if this is what what was needed. I will read the rust changelog tool readme again. |
I'm still getting the same error |
Ok will try solve |
It turns out that you can't create a changelog without details in a |
@nikitavoloboev Could you rename the latest release tag from Do you want me to generate a changelog now (without pushing the |
Id wait until your issue gets addressed. In the meanwhile we can look for another changelog generator that is good? |
Sounds good! |
How about Github Changelog Generator? It looks pretty nice and we can have Travis run it every time we push something ... the only downside is that it doesn't include commits (only issues and PRs) |
Not too fond of it. Lets wait for what the dev of rust changelog answers. |
Will do |
We should definitely use https://github.com/yoshuawuyts/changelog
The text was updated successfully, but these errors were encountered: