From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mx.groups.io with SMTP id smtpd.web11.686.1685457382018435747 for ; Tue, 30 May 2023 07:36:22 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=fBrpLKwa; spf=pass (domain: kernel.org, ip: 139.178.84.217, mailfrom: ardb@kernel.org) 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 779206167B for ; Tue, 30 May 2023 14:36:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id DCB70C4339E for ; Tue, 30 May 2023 14:36:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685457380; bh=kbqpsZFNy+as0jC+iBukq7+RRNNP2V8reKYXqM9aYGc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=fBrpLKwaP43+v1dSIWqkVjocFkaaNoQQDk8MIdaisuxc+bWxX9N9rQImszkH0xJDv FNh6C2GfYrNnM2DluRPd2DCPCmX0nSpFa3+sIuNVxtSRhctOHYMSi+JRbXkomWMPa3 KD70oohZBv75aZU654mVJMZ/wXgtqd0xW+zV2pAVNW5XF5s6JAI8JPLRjQVKx72Ext bTv+bvD/YpuFI8WuYLKBZg0s6eabK5OoDnlGj3oS6UGNMVQQlGbkkjVfypwfTv+IlW rTgeGI0ICo28gQhT2tDByr+1LpVMtXYlW3lE39CPQ2brQDqbAP918v5DIXcG2RCDdm +SF/bFB/0nyrQ== Received: by mail-lj1-f176.google.com with SMTP id 38308e7fff4ca-2af2451b3f1so48868761fa.2 for ; Tue, 30 May 2023 07:36:20 -0700 (PDT) X-Gm-Message-State: AC+VfDxBxrY2Az8XofmWOnNO/v9ubF3easzgVeGwObH8AW//etDl+E6V Cv0urMFFimA1L4fPCm20dgTDfANVYmYK0s9OJdA= X-Google-Smtp-Source: ACHHUZ6MoVTL9mAijzQSb8NEm3+FWCwdsHUwi/klDi/ZrFp8t5pi63TnOinzX7I9JyvqSZBeudS8y8nP0d3g9AKOfbs= X-Received: by 2002:a2e:9e89:0:b0:2af:2786:2712 with SMTP id f9-20020a2e9e89000000b002af27862712mr1020864ljk.25.1685457378860; Tue, 30 May 2023 07:36:18 -0700 (PDT) MIME-Version: 1.0 References: <4bcb9012-7e12-9df0-59a4-aff46b911c8f@bsdio.com> In-Reply-To: From: "Ard Biesheuvel" Date: Tue, 30 May 2023 16:36:07 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [edk2-devel] failed Pr To: devel@edk2.groups.io, michael.d.kinney@intel.com Cc: Sean Brogan , Rebecca Cran , "Kubacki, Michael" , "Gao, Liming" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 29 May 2023 at 18:45, Michael D Kinney wrote: > > Hi Sean, > > > > I see the =E2=80=9Crerun=E2=80=9D button on the =E2=80=9Cchecks=E2=80=9D = page of GitHub from my login. > > > > We have a mix of both Azure Pipelines and GitHub Actions today, so I thin= k it is important to see the =E2=80=9Crerun=E2=80=9D from GitHub view for M= aintainers. > Yes, that would be lovely. > > > This github page describes the feature, but not the permissions required. > > > > https://docs.github.com/en/actions/managing-workflow-runs/re-running-work= flows-and-jobs > > > > We currently have EDK II Maintainer Team set to =E2=80=9CTriage Role=E2= =80=9D permissions. From the table below, only =E2=80=9CWrite=E2=80=9D and= above are allowed to re-run. > > > > https://docs.github.com/en/organizations/managing-user-access-to-your-org= anizations-repositories/repository-roles-for-an-organization#permissions-fo= r-each-role > > > > =E2=80=9CWrite=E2=80=9D permissions add a lot of options, so I think we s= hould discuss tradeoffs in the next Tools/CI meeting. > > > > One option is to add a bot based on a new label to request failed jobs to= be re-run. The bot can use a token with permissions to re-run. > This would work for me - as long as I don't have to make changes to the branch, I'm happy with whatever we come up with.