[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [workflow] Automatically close bug report when a patch is committed

From: Vagrant Cascadian
Subject: Re: [workflow] Automatically close bug report when a patch is committed
Date: Thu, 07 Sep 2023 09:12:29 -0700

On 2023-09-07, Giovanni Biscuolo wrote:
> Hi Maxim and Ludovic,
> Maxim Cournoyer <> writes:
>> Giovanni Biscuolo <> writes:
>>> When I asket I though the best way would be to scan for a string like
>>> "Close #<bug-number>" in the commit message (the committer should add
>>> such a string) but probably this can be avoided: the bug can be closed
>>> when a patch is committed to one of the listed official brances (master,
>>> core-updates, etc.)
>> You mean by simply matching the subject?  Maybe that could work.
> Thinking twice maybe it's better to add a "Close: #<bug>" to the commit
> message.

Sooooo... I maintain the guix package in Debian, and want to make sure
that whatever bug-closing indicator guix upstream uses, does not end up
triggering when I push new upstream versions to ... and
start incorrectly marking incorrect bug numbers on that
were meant for

Currently that is:


"Close: #<bug>" is a bit nervously close; I could see a stray typo of an
extra "s" triggering the occasional very annoying problem.

I am much more comfortable with the "Fixes" convention of:


So, while I cannot insist here... I can plead a bit... and a namespaced
URL is kind of better in some ways anyways. :)

live well,

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]