From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A844C3858401; Tue, 24 Oct 2023 12:30:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A844C3858401 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1698150625; bh=OhJJUTphM2v0i+FRU80wVTqRXOJ3lVZ6xpewoTT0VPg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Taxh+IxKt7NXNhjXctX+z/H0QBqzx05g9cOT8YbToP4Pvvb9L+1Jhxr2jXWco3SET shigBLiL6DinVk3NPd5wyP/qskL+RSc1k+LYzQOESbrDYnKTkxz+clrOGN+oJiZ2YF zOQGqe5dxxYJV4a3AC0wyg4xbYGYzlg1iIMWBr1c= From: "carlos at redhat dot com" To: overseers@sourceware.org Subject: [Bug Infrastructure/30997] Automate patchwork committed marking Date: Tue, 24 Oct 2023 12:30:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: sourceware X-Bugzilla-Component: Infrastructure X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: overseers at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30997 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #2 from Carlos O'Donell --- 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 on= ly 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 committ= ed. 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 identif= ied more easily e.g. autoclose-bot. --=20 You are receiving this mail because: You are the assignee for the bug.=