From: "Li, Yi via groups.io" <yi1.li=intel.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] PR cannot be merged
Date: Fri, 20 Dec 2024 02:42:02 +0000 [thread overview]
Message-ID: <SJ1PR11MB6227E14EE69D89ED0DAEFD01C5072@SJ1PR11MB6227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN6PR11MB8244921693C80D58F4EC12198C072@MN6PR11MB8244.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
I think use mergify to rebase it can resolve it, I once encountered a related problem on a CryptoPkg patch
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ni, Ray via groups.io
Sent: Friday, December 20, 2024 10:31 AM
To: devel@edk2.groups.io
Cc: Ni, Ray <ray.ni@intel.com>
Subject: [edk2-devel] PR cannot be merged
All,
This PR Add fspiwrapper peim by hongbin123 * Pull Request #6292 * tianocore/edk2<https://github.com/tianocore/edk2/pull/6292> passed all review and CI checks but it just cannot be merged. I tried "Confirm rebase and merge" button but GitHub reports error "8 of 8 required status checks are expected."
anyone experienced similar issue and how it was resolved?
Thanks,
Ray
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120922): https://edk2.groups.io/g/devel/message/120922
Mute This Topic: https://groups.io/mt/110208943/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 4977 bytes --]
prev parent reply other threads:[~2024-12-20 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 2:30 [edk2-devel] PR cannot be merged Ni, Ray via groups.io
2024-12-20 2:42 ` Li, Yi via groups.io [this message]
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=SJ1PR11MB6227E14EE69D89ED0DAEFD01C5072@SJ1PR11MB6227.namprd11.prod.outlook.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