From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30997] Automate patchwork committed marking
Date: Tue, 24 Oct 2023 12:30:24 +0000 [thread overview]
Message-ID: <bug-30997-14326-SEamEz35VS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30997-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30997
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
I strongly recommend against it being a git hook since the hook involves
potentially complex code running on the git server, and the process need only
reach *eventual consistency* over time to support review of the patches in the
queue. Just like with an MR/PR workflow someone might commit a similar fix
ahead of you, and we'll never be able to keep the queue 100% automatically
clear.
My suggestion would be to write a bot that is run in a cron job as part of
patchwork.sourceware.org process automation, and that the bot account should
have maintainer status on all the projects and close the patches as committed.
As an evolving solution I would just have Siddhesh turn this on for all the
projects. I suggest a patchwork bot account to be used so it can be identified
more easily e.g. autoclose-bot.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-10-24 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 9:49 [Bug Infrastructure/30997] New: " mark at klomp dot org
2023-10-24 10:20 ` [Bug Infrastructure/30997] " siddhesh at sourceware dot org
2023-10-24 12:30 ` carlos at redhat dot com [this message]
2024-03-24 22:02 ` mark at klomp dot org
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=bug-30997-14326-SEamEz35VS@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).