Thank you Zbigniew and Miro for the link.

On 4/8/24 02:18, Zbigniew Jędrzejewski-Szmek wrote:

On Sun, Apr 07, 2024 at 09:08:49PM -0700, Carlos Rodriguez-Fernandez wrote:

...

On 4/7/24 21:07, Carlos Rodriguez-Fernandez wrote:

...

Not all commits correspond with a new release downstream, and not all commit messages are relevant to the end user to be part of the change log. For example, commits related with increasing gating test coverage efforts, or setting up gating.yaml itself. Another example is linting setting and/or configurations. How is that handled with autochangelog? Can we tell it to skip certain commits? Or should we include it all?

Yes, you can skip %changelog for some commits with '[skip changelog]' and provide additional content in the commit message which is not part of the changelog. See https://docs.pagure.org/fedora-infra.rpmautospec/autochangelog.html.

Zbyszek

On 4/7/24 23:01, Miro Hrončok wrote:

On 08. 04. 24 6:08, Carlos Rodriguez-Fernandez wrote:

...

Not all commits correspond with a new release downstream, and not all commit messages are relevant to the end user to be part of the change log. For example, commits related with increasing gating test coverage efforts, or setting up gating.yaml itself. Another example is linting setting and/or configurations. How is that handled with autochangelog? Can we tell it to skip certain commits? Or should we include it all?

Put [skip changelog] in the commit message.

https://fedora-infra.github.io/rpmautospec-docs/autochangelog.html#skipping-...