[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: convert everything to rpmautospec?
From:       Fabio Valentini <decathorpe () gmail ! com>
Date:       2024-04-11 10:48:44
Message-ID: CAB-QmhSJruMw=YOfYdHctQKQr3k02Fx+8Efd8pPOBag6A=Tk4A () mail ! gmail ! com
[Download RAW message or body]

On Thu, Apr 11, 2024 at 12:39 PM Leon Fauster via devel
<devel@lists.fedoraproject.org> wrote:
>
> Am 08.04.24 um 08:01 schrieb Miro Hrončok:
> > 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-changelog-entries
> >
>
> May be an [add rpmchangelog] would be more appropriate for some
> scenarios, where branching and merging or whatever would clutter
> the git log. Would lead to a more curated rpm changelog. Still,
> not ideal.

As far as I know, merge commits are already excluded automatically.

Fabio
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[prev in list] [next in list] [prev in thread] [next in thread]