From: Jakub Kicinski <kuba@kernel.org>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>
Subject: [ANN] pw-bot now recognizes all MAINTAINTERS
Date: Fri, 30 Jun 2023 08:58:38 -0700 [thread overview]
Message-ID: <20230630085838.3325f097@kernel.org> (raw)
Hi!
tl;dr pw-bot now cross references the files touched by a *series* with
MAINTAINERS and gives access to all patchwork states to people listed
as maintainers (email addrs must match!)
During the last merge window we introduced a new pw-bot which acts on
simple commands included in the emails to set the patchwork state
appropriately:
https://lore.kernel.org/all/20230508092327.2619196f@kernel.org/
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#updating-patch-status
This is useful in multiple ways, the two main ones are that (1) general
maintainers have to do less clicking in patchwork, and that (2) we have
a log of state changes, which should help answer the question "why
is my patch in state X":
https://patchwork.hopto.org/pw-bot.html
The bot acts automatically on emails from the kbuild bot. Author of
the series can also discard it from patchwork (but not bring it back).
Apart from that maintainers and select reviewers had access rights
to the commands. Now the bot has been extended to understand who the
maintainers are on series-by-series basis, by consulting MAINTAINERS.
Anyone who is listed as a maintainer of any files touched by the series
should be able to change the state of the series, both discarding it
(e.g. changes-requested) and bringing it back (new, under-review).
The main caveat is that the command must be sent from the email listed
in MAINTAINERS. I've started hacking on aliasing emails but I don't
want to invest too much time unless it's actually a problem, so please
LMK if this limitation is stopping anyone from using the bot.
The names of the states and their shortcuts are in the source code:
https://github.com/kuba-moo/nipa/blob/master/mailbot.py#L46
next reply other threads:[~2023-06-30 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 15:58 Jakub Kicinski [this message]
2023-07-01 14:04 ` [ANN] pw-bot now recognizes all MAINTAINTERS Toke Høiland-Jørgensen
2023-07-01 23:38 ` Jakub Kicinski
2023-07-03 13:19 ` Toke Høiland-Jørgensen
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=20230630085838.3325f097@kernel.org \
--to=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).