Problem with bumping changelog

[devsheva]

I'm trying to generate a new whole changelog with already present a first tag.

I tried doing

• git cliff -o --> leads to a changelog with all commits under unreleased
• git cliff --bump -o --> leads to a changelog with all commits under next tag

Context: already present a 1.0.0 tag

My goal is to achieve a changelog like:

# Changelog

All notable changes to this project will be documented in this file.

## [1.0.1] - <date>

....

## [1.0.0] - <date>
....

[orhun]

Hello!

git cliff --bump -o --> leads to a changelog with all commits under next tag

Yup, that's the correct usage. Is the problem that you're not getting the next tag you're expecting?

[orhun]

I created a new issue: #804

So what should I do to achieve my goal?

Nothing as of now, until that feature is implemented. But you can probably just comment out that line and build from source for achieving the correct behavior.

[devsheva]

Sorry, maybe I'm too dumb but I have two final questions.
First, what is exactly topological order for commits? Is it like grouping by type of commit or am I wrong?
Second, i have installed the package from homebrew. The correct behaviour can be achieved only with building from source or is it possible to do it with something else?

[orhun]

First, what is exactly topological order for commits? Is it like grouping by type of commit or am I wrong?

I also look it up every time so it would be better to check out this Stack Overflow issue since I'm not sure I can explain it the best.

The --topo-order switch simply (or complicated-ly, as the case actually is) modifies the priority of the commits as Git marches down the two legs of the merge, so that you get everything from one leg, then everything from the other.

Second, i have installed the package from homebrew. The correct behaviour can be achieved only with building from source or is it possible to do it with something else?

Yup, only with building from source after commenting out line 79 in repo.rs.

[devsheva]

What shall we do with this discussion now?

P.S. Thank you so much for the prompt answers

[orhun]

Let's keep it open until #804 is implemented. I will let you know 🐻