Updated CHANGELOG.md #788
Merged
Updated CHANGELOG.md #788
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Sep 7, 2016
Closed
…erator Used the following CLI command argument to create CHANGELOG.md github_changelog_generator \ -u liip \ -p LiipImagineBundle \ -t <hidden> \ --no-issues \ --simple-list fixed duplicate changelog generation run
robfrawley
force-pushed
the
feature-add-changelog
branch
from
90584f6 to
1c5302f
Compare
|
lgtm! 👍 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull-request resolves #786 and replaces #781. I've created a new, auto-generated
CHANGELOG.mdthat details pull-requests per-release, according to the GitHub API.The option to both remove and update the changelog has been thrown around: I hold the opinion that the changelog serves an important purpose by providing a historical overview of the code activity regardless of the delivery means used to acquire the source code. As such, I propose we merge a new changelog updated to accurately reflect this repositories activity.
Per issue #786, I used the skywinder/github-changelog-generator executable to generate the new changelog file. I fumbled with a few different combinations of command arguments, and settled on the following, which offered the cleanest result, in my opinion.
If someone else decides to download skywinder/github-changelog-generator and lands on a better argument combination, I'm open to changing it if any strong opinions are voiced.