feat: go template function uniqueOlderCommits/uniqueNewerCommits is available #211
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.
Closes #29
What does this do / why do we need it?
uniqueOlderCommits
anduniqueNewerCommits
. They removes duplicated commits / log entries. "Duplicated" is evaluated withfields
specified. For example, if your changelog entries consists of.Scope
and.Subject
,(uniqueOlderCommits .Commits "Scope" "Subject")
is expected.We can rewrite
.chglog/CHANGELOG.tpl.md
ingit-chglog
like this:How this PR fixes the problem?
Commit
to remove duplication.Commit
. For example, "Scope" and "Subject". Or it may beJiraIssueID
(for the case only one entry for one ticket).uniqueOlderCommits
anduniqueNewerCommits
resolves that.What should your reviewer look out for in this PR?
README.md
. This feature is too complicated for my English.Check lists
Additional Comments (if any)
Older
andNewer
means the commit order. I believe we also need fix: the sort order of commits is unstable #210 to have this feature fully functioned.Which issue(s) does this PR fix?
fixes #29