You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In repositories with multiple branches, git log is not enough to get all the tags. Sometimes tags only appear in release branches.
Describe the solution you'd like
Add an option to work on every branches. This is possible with the --all flag of git log.
Describe alternatives you've considered
Checking out specific branches to run git-changelog. This is very limited.
Additional context
When working on all commits (git log --all), we must ensure the following things when building the versions:
versions must be sorted semantically, not chronologically. For example, given versions 1, 2, 1.1 and 3 were published in that order, the versions must be chained as 3 -> 2 -> 1.1 -> 1, not 3 -> 1.1 -> 2 -> 1.
versions must be rendered chronologically: if we just published a patch to an old version, it should still appear at the top of the changelog, not lower, and be compared against its semantic previous version.
Boost priority
Boost priority in our backlog through Polar.sh. Higher pledge, higher priority.
Minimum pledge by user/organization is $5, minimum amount for boost is $30.
…semver)
Before, a commit was assigned the version/tag that happened next in the timeline. This leads to versions referencing commits that are not ancestors of it (and therefore not part of this version).
Instead the versions should contain only all commits that are ancestors, up until a new version is encountered.
Issue-70: #70
Issue-42: #42
PR-72: #72
Co-authored-by: Timothée Mazzucotelli <[email protected]>
Is your feature request related to a problem? Please describe.
In repositories with multiple branches,
git log
is not enough to get all the tags. Sometimes tags only appear in release branches.Describe the solution you'd like
Add an option to work on every branches. This is possible with the
--all
flag ofgit log
.Describe alternatives you've considered
Checking out specific branches to run
git-changelog
. This is very limited.Additional context
When working on all commits (
git log --all
), we must ensure the following things when building the versions:3 -> 2 -> 1.1 -> 1
, not3 -> 1.1 -> 2 -> 1
.Boost priority
The text was updated successfully, but these errors were encountered: