-
Notifications
You must be signed in to change notification settings - Fork 66
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 CHANGELOG.md
#349
Add CHANGELOG.md
#349
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we are going to have a changelog (which I think is a good idea) we should have a note on the README.md asking contributors to add a note to the changelog as part of their PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed in office hours and decided to have changelog, and that we are aiming to have it for all linebender projects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the grander scheme of things we want to have even better changelogs and a whole workflow on how they get continuously maintained. However none of that needs to happen in this PR.
Thanks for taking this step and getting us going!
@xStrom Should I rebase, squash or merge commit? :) |
Good question - IIRC we talked about it and prefer squash commits, but I may be wrong. I don't think it matters too much. |
Squash, merge queues will arrive sometime in the future. 😆 |
No description provided.