Reviewed-by: Rebecca Cran <rebe...@bsdio.com>
On 2/13/23 09:04, Michael Kubacki wrote:
From: Michael Kubacki <michael.kuba...@microsoft.com>
PR builds and CI are currently broken due to a mergify brownout
today because edk2 uses the `rebase_fallback` attribute of the
`queue` action.
Message from Mergify/Summary:
```
The configuration uses the deprecated rebase_fallback attribute
of the queue action.
A brownout is planned on February 13th, 2023.
This option will be removed on March 13th, 2023.
For more information: https://docs.mergify.com/actions/queue/
```
Therefore, this change removes the attribute per the guidance in
the following changelog message to retain existing behavior.
https://changelog.mergify.com/changelog/rebasefallback-is-deprecated
```
The option rebase_fallback is now deprecated and should not be
used anymore.
Mergify will always report errors in the future if a rebase merge
is impossible.
```
Cc: Michael D Kinney <michael.d.kin...@intel.com>
Cc: Liming Gao <gaolim...@byosoft.com.cn>
Cc: Sean Brogan <sean.bro...@microsoft.com>
Signed-off-by: Michael Kubacki <michael.kuba...@microsoft.com>
---
Notes:
PR with change is here:
https://github.com/tianocore/edk2/pull/4035
.mergify/config.yml | 1 -
1 file changed, 1 deletion(-)
diff --git a/.mergify/config.yml b/.mergify/config.yml
index bd6da4c77937..3471896a3495 100644
--- a/.mergify/config.yml
+++ b/.mergify/config.yml
@@ -38,7 +38,6 @@ pull_request_rules:
actions:
queue:
method: rebase
- rebase_fallback: none
name: default
- name: Post a comment on a PR that can not be merged due to a merge conflict
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#100128): https://edk2.groups.io/g/devel/message/100128
Mute This Topic: https://groups.io/mt/96938743/21656
Group Owner: devel+ow...@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
