From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <michael.d.kinney@intel.com>
Cc: "'Sean Brogan'" <sean.brogan@microsoft.com>,
"'Bret Barkelew'" <Bret.Barkelew@microsoft.com>
Subject: 回复: [edk2-devel] [Patch 1/1] .mergify: Enable Mergify for stable/* branches
Date: Mon, 21 Dec 2020 09:19:39 +0800 [thread overview]
Message-ID: <012901d6d737$5c9e0000$15da0000$@byosoft.com.cn> (raw)
In-Reply-To: <20201219024715.2000-1-michael.d.kinney@intel.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> -----邮件原件-----
> 发件人: bounce+27952+69247+4905953+8761045@groups.io
> <bounce+27952+69247+4905953+8761045@groups.io> 代表 Michael D
> Kinney
> 发送时间: 2020年12月19日 10:47
> 收件人: devel@edk2.groups.io
> 抄送: Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew
> <Bret.Barkelew@microsoft.com>; Liming Gao <gaoliming@byosoft.com.cn>
> 主题: [edk2-devel] [Patch 1/1] .mergify: Enable Mergify for stable/*
> branches
>
> https://bugzilla.tianocore.org/show_bug.cgi?id=3130
>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
> ---
> .mergify/config.yml | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/.mergify/config.yml b/.mergify/config.yml
> index 26583de0f631..9774aaf49774 100644
> --- a/.mergify/config.yml
> +++ b/.mergify/config.yml
> @@ -16,7 +16,7 @@
> # * This file must be checked into the 'default' branch of a repo.
Copies
> # of this file on other branches of a repo are ignored by Mergify.
> #
> -# Copyright (c) 2019, Intel Corporation. All rights reserved.<BR>
> +# Copyright (c) 2019 - 2020, Intel Corporation. All rights reserved.<BR>
> # SPDX-License-Identifier: BSD-2-Clause-Patent
> #
> # https://github.com/apps/mergify
> @@ -28,7 +28,7 @@ pull_request_rules:
>
> - name: Automatically merge a PR when all required checks pass and
> 'push' label is present
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - label=push
> - author=@tianocore/edk-ii-maintainers
> - status-success=tianocore.PatchCheck
> @@ -41,7 +41,7 @@ pull_request_rules:
>
> - name: Automatically close a PR when all required checks pass and
'push'
> label is not present
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - -label=push
> - -closed
> - status-success=tianocore.PatchCheck
> @@ -55,7 +55,7 @@ pull_request_rules:
>
> - name: Post a comment on a PR that can not be merged due to a merge
> conflict
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - conflict
> actions:
> comment:
> @@ -63,7 +63,7 @@ pull_request_rules:
>
> - name: Automatically close a PR that fails the EDK II Maintainers
> membership check and 'push' label is present
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - label=push
> - -author=@tianocore/edk-ii-maintainers
> actions:
> @@ -72,7 +72,7 @@ pull_request_rules:
>
> - name: Post a comment on a PR if PatchCheck fails
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - status-failure=tianocore.PatchCheck
> actions:
> comment:
> @@ -80,7 +80,7 @@ pull_request_rules:
>
> - name: Post a comment on a PR if Ubuntu GCC5 fails
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - status-failure=Ubuntu GCC5 PR
> - status-success=Ubuntu GCC5 PR (FAILED)
> actions:
> @@ -89,7 +89,7 @@ pull_request_rules:
>
> - name: Post a comment on a PR if Windows VS2019 fails
> conditions:
> - - base=master
> + - base~=(^master|^stable/)
> - status-failure=Windows VS2019 PR
> - status-success=Windows VS2019 PR (FAILED)
> actions:
> --
> 2.29.2.windows.2
>
>
>
>
>
prev parent reply other threads:[~2020-12-21 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 2:47 [Patch 1/1] .mergify: Enable Mergify for stable/* branches Michael D Kinney
2020-12-21 1:19 ` gaoliming [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='012901d6d737$5c9e0000$15da0000$@byosoft.com.cn' \
--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