workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: workflows@vger.kernel.org, aros@gmx.com,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	tools@linux.kernel.org
Subject: Re: Introducing bugbot
Date: Tue, 4 Apr 2023 08:36:07 -0400	[thread overview]
Message-ID: <20230404-bacteria-refinery-a97393@meerkat> (raw)
In-Reply-To: <b38de7ff-3de1-cd4a-a532-66642aea587c@leemhuis.info>

On Tue, Apr 04, 2023 at 07:58:40AM +0200, Thorsten Leemhuis wrote:
> Would be great if bugbot could CC the regressions list for all bugs that
> have the regressions flag set to "yes"

I'll see if I can add this logic and make it configurable.

> How does one make bugbot forward a bug to everyone in the signed-off-by
> chain of a commit that caused a regression, which might or might not
> have a bugzilla account?  When the reporter performed a bisection these
> are the primary contacts that need to be reached out to, but the
> maintainers and lists for the subsystem obviously should be CCed.

I can add a cf_bisected_commit field that can take a commit-id. When gathering
recipients, we can check if we know that commit in one of the tracked
repositories, and get the author field out of it. Would that be sufficient, or
do we need to run get_maintainer on it for a full picture?

Note, that you can also add addresses to Cc: on the thread -- they will be
collected behind the scenes as each message is processed and any bugbot
notifications originating from the bugzilla side will also include them.

-K

  parent reply	other threads:[~2023-04-04 12:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 21:45 Konstantin Ryabitsev
2023-04-03 21:47 ` Kernel.org Bugbot
2023-04-03 21:51   ` Konstantin Ryabitsev
2023-04-04  5:58 ` Thorsten Leemhuis
2023-04-04  6:57   ` Geert Uytterhoeven
2023-04-04  8:16   ` Bagas Sanjaya
2023-04-04 12:36   ` Konstantin Ryabitsev [this message]
2023-04-04 12:55     ` Thorsten Leemhuis
2023-04-04 16:16 ` Artem S. Tashkinov
2023-04-04 17:25   ` Mark Brown
2023-04-04 17:35   ` Konstantin Ryabitsev
2023-04-04 21:39     ` David Sterba
2023-04-08 12:10 ` Thorsten Leemhuis
2023-04-12 12:23   ` Kalle Valo
2023-04-12 14:07     ` Konstantin Ryabitsev
2023-04-12 16:47       ` Kalle Valo
2023-05-05 15:52 ` Jakub Kicinski
2023-05-05 19:12   ` Konstantin Ryabitsev
2023-05-05 19:32     ` Jakub Kicinski
2023-05-05 19:39       ` Konstantin Ryabitsev
2023-05-05 19:43         ` Jakub Kicinski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230404-bacteria-refinery-a97393@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=aros@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=tools@linux.kernel.org \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox