Open menicosia opened 9 years ago
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/101643482.
Thank you, Marco. I'll admit, in the release notes I assembled for cf-release 215 I felt some annoyance with the duplicates. I have had a story for this for a few weeks, unprioritized: https://www.pivotaltracker.com/story/show/100051336
Do you find value in the response still being grouped by repo? I still like this format. With this in mind, I've considered that the de-duping would be done only within a repo in the response. In other words, a story might be reference for multiple repos, but only once within each repo.
I'm included to keep the link as "details" for now, as this has historically been how cf-release release notes are formatted.
I have only been using this tool for Lattice releases, which up until just about now, have been a single repo.
Splitting Lattice out is "planned for some indefinite point in the future" so I don't know when I'll get to play with that portion of the functionality.
-- Marco N.
Hi guys,
This isn't a high priority for me. But I thought you might want to know what I do in order to massage
git_repo_changelog
output into the format that my anchor prefers. You can see our pattern in the Lattice v0.3.0 release notes.sort -u
now.[details]
we use[#STORYNUMBER]
. If you are inclined to do the same, it'd save me the extra sed step.Anyways, thank you for fixing my last bug, I totally love this tool.
Marco Nicosia Product Manager Pivotal Software, Inc.