These are from four/five distinct events with 1-2 emails each: two
commits, sonarcloud pass, the merge, and finally deleting the branch.
(actually _four_ events, sonarcloud is trigger by commit I think)
One solution may be to have only the PR description in the header so
that all emails concerning a single PR end up in the same thread. I
doubt though that this is technically possible (or desirable).
Maybe we can stop Sonartype from sending emails? Or send them only if it
actually fails?
I am also not sure why we get two emails for the merge.
Til
On 08/07/2023 01:33, Craig Russell wrote:
There are over half a dozen messages regarding JDO-827/PR#81.
Is there a problem with the asf.yaml configuration that prevents these from
being threaded?
I know we updated asf.yaml recently but somehow this does not meet my
expectations.
Thanks,
Craig
Begin forwarded message:
From: Tilmann <notificati...@github.com>
Subject: Re: [apache/db-jdo] JDO-827 Simplify JNDI (PR #81)
Date: July 6, 2023 at 11:43:49 PDT
To: apache/db-jdo <db-...@noreply.github.com>
Cc: Subscribed <subscri...@noreply.github.com>
Reply-To: apache/db-jdo
<reply+ad4m6rbfjgvd5iolfl6juo6cwq66levbnhhgujt...@reply.github.com>
Merged #81 <https://github.com/apache/db-jdo/pull/81> into main.
—
Reply to this email directly, view it on GitHub
<https://github.com/apache/db-jdo/pull/81#event-9746958051>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4M6RCW3D3TOUV7QNSTPXLXO4BOLANCNFSM6AAAAAAZYSIERU>.
You are receiving this because you are subscribed to this thread.
Craig L Russell
c...@apache.org
