Skip to content
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

Better handling of multiple branches #42

Open
pawamoy opened this issue Mar 14, 2023 · 0 comments
Open

Better handling of multiple branches #42

pawamoy opened this issue Mar 14, 2023 · 0 comments
Labels
feature New feature or request fund Issue priority can be boosted

Comments

@pawamoy
Copy link
Owner

pawamoy commented Mar 14, 2023

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.
  • View all issues with pledges.
  • We receive the funds once the issue is completed and confirmed by you.
  • Features with the insiders label are released to sponsors first, and tied to a funding goal.
Fund with Polar
pawamoy added a commit that referenced this issue Mar 14, 2024
…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]>
@pawamoy pawamoy added feature New feature or request fund Issue priority can be boosted labels Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request fund Issue priority can be boosted
Projects
None yet
Development

No branches or pull requests

1 participant