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>,
"'Bob Feng'" <bob.c.feng@intel.com>,
"'Yuwei Chen'" <yuwei.chen@intel.com>
Subject: 回复: [edk2-devel] [Patch 0/3] Mergify Enhancements
Date: Fri, 9 Jul 2021 13:09:25 +0800 [thread overview]
Message-ID: <007c01d77480$9670f4e0$c352dea0$@byosoft.com.cn> (raw)
In-Reply-To: <20210708034902.1608-1-michael.d.kinney@intel.com>
Reviewed-by: Liming Gao <gaoliming@byosoft.com.cn>
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael D
> Kinney
> 发送时间: 2021年7月8日 11:49
> 收件人: devel@edk2.groups.io
> 抄送: Sean Brogan <sean.brogan@microsoft.com>; Bret Barkelew
> <Bret.Barkelew@microsoft.com>; Liming Gao <gaoliming@byosoft.com.cn>;
> Bob Feng <bob.c.feng@intel.com>; Yuwei Chen <yuwei.chen@intel.com>
> 主题: [edk2-devel] [Patch 0/3] Mergify Enhancements
>
> * Removed FINISHED and FAILED states with 10 second delays
> * Update PatchCheck.py to ignore commit message format issues
> in merge commeits added by Merfigy.
> * Enable Mergify queue feature to support auto rebase when
> 'push' label is set and gauarntee that all EDK II CI checks
> are run before merging in changes with linear history.
> * Use status checks configured in GitHub branch protections
> * Allow non EDK II Maintainers to create a PR
> Requires an EDK II Maintainer to accept the change and
> request merge by adding 'push' label. Only EDK II Maintainers
> have ability to set/clear labels.
> * Do not automatically close PRs for personal builds.
>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> Cc: Liming Gao <gaoliming@byosoft.com.cn>
> Cc: Bob Feng <bob.c.feng@intel.com>
> Cc: Yuwei Chen <yuwei.chen@intel.com>
> Signed-off-by: Michael D Kinney <michael.d.kinney@intel.com>
>
> Michael D Kinney (3):
> BaseTools/Scripts: Ignore Mergify merge commits in PatchCheck.py
> .mergify: Simplify Mergify rules using GitHub status checks
> .azurepipelines: Remove FINISHED and FAILED states
>
> .../templates/pr-gate-build-job.yml | 20 ------
> .mergify/config.yml | 71 ++++---------------
> BaseTools/Scripts/PatchCheck.py | 18 +++--
> 3 files changed, 24 insertions(+), 85 deletions(-)
>
> --
> 2.32.0.windows.1
>
>
>
>
>
prev parent reply other threads:[~2021-07-09 5:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 3:48 [Patch 0/3] Mergify Enhancements Michael D Kinney
2021-07-08 3:49 ` [Patch 1/3] BaseTools/Scripts: Ignore Mergify merge commits in PatchCheck.py Michael D Kinney
2021-07-08 3:55 ` [EXTERNAL] [edk2-devel] " Bret Barkelew
2021-07-09 5:30 ` Bob Feng
2021-07-08 3:49 ` [Patch 2/3] .mergify: Simplify Mergify rules using GitHub status checks Michael D Kinney
2021-07-08 3:55 ` [EXTERNAL] " Bret Barkelew
2021-07-08 3:49 ` [Patch 3/3] .azurepipelines: Remove FINISHED and FAILED states Michael D Kinney
2021-07-08 3:51 ` [EXTERNAL] " Bret Barkelew
2021-07-09 5:09 ` 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='007c01d77480$9670f4e0$c352dea0$@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