public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, michael.d.kinney@intel.com
Cc: Sean Brogan <spbrogan@outlook.com>,
	Rebecca Cran <rebecca@bsdio.com>,
	 "Kubacki, Michael" <michael.kubacki@microsoft.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>
Subject: Re: [edk2-devel] failed Pr
Date: Tue, 30 May 2023 16:36:07 +0200	[thread overview]
Message-ID: <CAMj1kXH96Y+_qC8wXwHpN+daCTHfjq2JJFNZg-42cb9Q0MsKEw@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB492965340B2B53890CF6B9B9D24A9@CO1PR11MB4929.namprd11.prod.outlook.com>

On Mon, 29 May 2023 at 18:45, Michael D Kinney
<michael.d.kinney@intel.com> wrote:
>
> Hi Sean,
>
>
>
> I see the “rerun” button on the “checks” page of GitHub from my login.
>
>
>
> We have a mix of both Azure Pipelines and GitHub Actions today, so I think it is important to see the “rerun” from GitHub view for Maintainers.
>

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-workflows-and-jobs
>
>
>
> We currently have EDK II Maintainer Team set to “Triage Role” permissions.  From the table below, only “Write” and above are allowed to re-run.
>
>
>
> https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role
>
>
>
> “Write” permissions add a lot of options, so I think we should 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.

  reply	other threads:[~2023-05-30 14:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29 12:48 failed Pr Ard Biesheuvel
2023-05-29 12:55 ` [edk2-devel] " Attar, AbdulLateef (Abdul Lateef)
2023-05-29 14:37 ` Rebecca Cran
2023-05-29 14:44   ` Ard Biesheuvel
2023-05-29 15:12     ` Sean
2023-05-29 15:13       ` Michael D Kinney
2023-05-29 15:37         ` Sean
2023-05-29 15:43           ` Rebecca Cran
2023-05-29 16:44           ` Michael D Kinney
2023-05-30 14:36             ` Ard Biesheuvel [this message]
2023-05-30 15:34               ` Michael D Kinney
2023-05-30 15:45                 ` Ard Biesheuvel
2023-05-30 17:26                   ` Michael D Kinney
  -- strict thread matches above, loose matches on Subject: below --
2023-06-02 16:19 failed pr Ard Biesheuvel
2023-06-02 16:36 ` [edk2-devel] " Michael D Kinney
2023-06-02 16:38   ` Michael D Kinney
2023-06-02 22:32     ` Ard Biesheuvel
2023-06-02 23:38       ` Ard Biesheuvel
2023-06-03  0:07         ` Michael D Kinney
2023-06-06 19:55           ` Michael D Kinney
2023-06-06 21:37             ` Ard Biesheuvel
2023-06-07  2:02             ` Wu, Hao A
2023-06-07  3:07               ` Michael D Kinney
2023-06-07  3:15                 ` Wu, Hao A
2023-06-07 15:09                   ` Ard Biesheuvel
2023-06-07 15:39                     ` Rebecca Cran
2023-06-07 17:00                       ` Ard Biesheuvel
2023-06-07 17:02                         ` Rebecca Cran
2023-06-07 17:03                           ` Ard Biesheuvel

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-list 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=CAMj1kXH96Y+_qC8wXwHpN+daCTHfjq2JJFNZg-42cb9Q0MsKEw@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /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