From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Michael Kubacki <mikuback@linux.microsoft.com>,
Sean Brogan <sean.brogan@microsoft.com>
Subject: Re: [edk2-devel] failed pr
Date: Tue, 6 Jun 2023 23:37:40 +0200 [thread overview]
Message-ID: <CAMj1kXG8+uY8Z8u6ebVUWfV+DPd79C81bD35Pu4+sD+a+gBdxQ@mail.gmail.com> (raw)
In-Reply-To: <CO1PR11MB4929ECD2A331B449CF05E5BCD252A@CO1PR11MB4929.namprd11.prod.outlook.com>
On Tue, 6 Jun 2023 at 21:55, Kinney, Michael D
<michael.d.kinney@intel.com> wrote:
>
> All EDK II Maintainers should now have permissions to "re-run failed jobs".
>
> If you see a PR with failed jobs that are not related to the code change,
> then try rerunning the specific failed job or select "re-run failed jobs"
> from the drop down in top right of "Checks" tab.
>
> Please let me know if you do not see this as an option.
>
Excellent! Thanks for taking care of this.
next prev parent reply other threads:[~2023-06-06 21:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2023-05-30 15:34 ` Michael D Kinney
2023-05-30 15:45 ` Ard Biesheuvel
2023-05-30 17:26 ` Michael D Kinney
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=CAMj1kXG8+uY8Z8u6ebVUWfV+DPd79C81bD35Pu4+sD+a+gBdxQ@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