-
Notifications
You must be signed in to change notification settings - Fork 46
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
Replace single changelog with one for each gem. #127
Conversation
But now we won't know what changed! What's the long term fix? I imagine we can combine the gems or have a CHANGELOG in each? |
@dblock The commit messages will serve this purpose. Whenever you draft a new release, Github will pull the info of all commits since the last release for you to edit. With 5 gems, each with its own version number, the long term solution is having a Changelog for each gem. It's the automated enforcement of changelog that's giving us trouble because it only works for 1 changelog file per repo. For now we're going to ask people to update the appropriate changelog when they offer a PR. |
@nhtruong I don't think we need the |
LGTM, needs a rebase |
With multiple gems coexisting in the same repo, the current framework for CHANGELOG.md is not suitable. We're going with a changelog for each gem and disable changelog verifier since it can't handle multiple change logs yet. Signed-off-by: Theo Truong <[email protected]>
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.
One of the problems with having all these gems in the same repo is tagging. Do we really want all of this to be lumped together if effectively we develop and release them separately? I opened #133 to discuss.
With multiple gems coexisting in the same repo, the current framework for CHANGELOG.md is not suitable. We're going with a changelog for each gem and disable changelog verifier since it can't handle multiple change logs yet.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.