From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CD7F7C77B7D for ; Fri, 5 May 2023 19:33:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233311AbjEETdP (ORCPT ); Fri, 5 May 2023 15:33:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58052 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233553AbjEETcu (ORCPT ); Fri, 5 May 2023 15:32:50 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C4D9AA5DD; Fri, 5 May 2023 12:32:28 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 61C6E64028; Fri, 5 May 2023 19:32:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 943A5C433D2; Fri, 5 May 2023 19:32:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1683315147; bh=uIYZDSLkos+kOTYYQ2APOo0jrdAuVxmIhuS9ORUHscA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=DkoV+rO6rWjTu8eduoeaimH2kFB1k5WM25kGWtXs76/7hnTGQAZ8gD2OnYDDeM8LD 6243wdWcCvo+jjuJ780cirSCz+EWkEELo0D70eOeniKhyMxbpHpM2+6ZkQb9e5ShbF wWHTIITX7lFLSRtaj4kFolEMcm0iw+GEbkixDsBr8gWnce44EK9biBFiBVUs10pEzl nS5uOSqGCV1SUdDNNm+rnFA1Pf+0j2AuwcPIUOfJg7iKjIkdkJWQuZvoy1CYgRnc4Y YABjDLRX2UH+NJ0lw7e7YTcv0HYs/SnG1KYB6uRoSMVOIOqDiSN1ZKnB3mByUsjOwW uZ4oqKmCFwAUg== Date: Fri, 5 May 2023 12:32:26 -0700 From: Jakub Kicinski To: Konstantin Ryabitsev Cc: workflows@vger.kernel.org, aros@gmx.com, linux-kernel@vger.kernel.org, regressions@lists.linux.dev, tools@linux.kernel.org, linux@leemhuis.info Subject: Re: Introducing bugbot Message-ID: <20230505123226.731d8ff8@kernel.org> In-Reply-To: <20230505-lent-swoosh-4897e2@meerkat> References: <20230505085218.60c62d75@kernel.org> <20230505-lent-swoosh-4897e2@meerkat> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: workflows@vger.kernel.org On Fri, 5 May 2023 15:12:02 -0400 Konstantin Ryabitsev wrote: > On Fri, May 05, 2023 at 08:52:18AM -0700, Jakub Kicinski wrote: > > > Per our discussion last fall, I've been working on a bridge between bugzilla > > > and public-inbox, which went live in the past few days. It's still a very > > > early release, but it can do the following: > > > > What about closing the bugs once they had been fixed/triaged/proven > > invalid? > > For now, bugbot can look at a branch in a git repo and close bugs when it sees > a matching "Closes:" trailer. Interesting. Obviously that assumes the bug needs a fix, and we're talking bugzilla so lots of clueless people lobbing non-issues at us. But also - Closes: is a legit trailer now? I thought we only allow Link: In any case - I'm guessing I just don't have permissions to close the issues via web. Is your preference to iterate on the bot or maintainers to request permissions in BZ (how?)?