public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [Patch v5 21/22] .mergify: Add Mergify YML pull request rules configuration file
Date: Fri, 17 Jan 2020 20:29:12 +0000	[thread overview]
Message-ID: <20200117202912.GO20629@bivouac.eciton.net> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9E5FD0E@ORSMSX113.amr.corp.intel.com>

Hi Mike,

Many thanks for resolving!
I'll try your other suggestions if this happens again in future.

Best Regards,

Leif

On Fri, Jan 17, 2020 at 20:22:03 +0000, Kinney, Michael D wrote:
> Hi Leif,
> 
> I have not tried the mergify commands like that.  I can investigate
> further if we think we need them.
> 
> I saw that some of the Azure pipelines checks did not run.  That
> Is what was blocking Mergify.  Mergify was waiting for status.
> 
> I did a Close and Re-open to re-trigger Azure Pipelines and that
> worked.  You changed have been committed.
> 
> We have seen a very rare condition in communication between 
> Azure Pipelines and GitHub.  This close/re-open is what we
> can try first.  The 2nd approach is to abandon the current
> PR and create a new PR with the same content.  That has only
> had to be used once since enabling in early November.
> 
> Mike
> 
> > -----Original Message-----
> > From: Leif Lindholm <leif.lindholm@linaro.org>
> > Sent: Friday, January 17, 2020 11:44 AM
> > To: Kinney, Michael D <michael.d.kinney@intel.com>
> > Cc: devel@edk2.groups.io
> > Subject: Re: [edk2-devel] [Patch v5 21/22] .mergify:
> > Add Mergify YML pull request rules configuration file
> > 
> > Hi Mike (on-list),
> > 
> > Embarassing to admit, but I hadn't tried to do my first
> > mergify commit
> > until the Maintainers.txt right now, and that isn't
> > working as I expected.
> > 
> > I tried to force a retry on
> > https://github.com/tianocore/edk2/pull/307
> > (since I added the 'push' tag *after* submitting the
> > github pull
> > request), but as you can see mergify says
> > "@leiflindholm is not allowed
> > to run commands".
> > 
> > Am I missing something obvious?
> > 
> > Best Regards,
> > 
> > Leif
> > 
> > On Mon, Nov 11, 2019 at 00:41:06 -0800, Michael D
> > Kinney wrote:
> > > Add directory for the Mergify YML configuration files
> > that
> > > provides rules and actions used to process a pull
> > request.
> > >
> > > * Auto commit a PR from EDK II Maintainer with 'push'
> > label
> > >   set and all CI checks pass
> > > * Auto close a PR from any developers without 'push'
> > label
> > >   set and all CI checks pass.
> > > * Auto close a PR from a non EDK II Maintainer that
> > has
> > >   the 'push' label set.
> > > * Post a comment to a PR that has a merge conflict.
> > >   Submitter can resolved conflicts and reopen the PR.
> > > * Post a comment to a PR that fails PatchCheck.py
> > >   Submitter can resolve PatchCheck.py issues and
> > >   reopen the PR.
> > >
> > > Cc: Liming Gao <liming.gao@intel.com>
> > > Cc: Sean Brogan <sean.brogan@microsoft.com>
> > > Cc: Bret Barkelew <Bret.Barkelew@microsoft.com>
> > > Signed-off-by: Michael D Kinney
> > <michael.d.kinney@intel.com>
> > > Reviewed-by: Liming Gao <liming.gao@intel.com>
> > > ---
> > >  .mergify/config.yml | 97
> > +++++++++++++++++++++++++++++++++++++++++++++
> > >  1 file changed, 97 insertions(+)
> > >  create mode 100644 .mergify/config.yml
> > >
> > > diff --git a/.mergify/config.yml
> > b/.mergify/config.yml
> > > new file mode 100644
> > > index 0000000000..26583de0f6
> > > --- /dev/null
> > > +++ b/.mergify/config.yml
> > > @@ -0,0 +1,97 @@
> > > +## @file
> > > +# Mergify YML file that automatically merges a
> > GitHub pull request against
> > > +# edk2-ci if all of the GitHub branch protections
> > have passed.  It also
> > > +# contains rules to:
> > > +# * auto close branches that are not from an EDK II
> > Maintainer
> > > +# * post a comment on pull requests that have merge
> > conflicts.
> > > +# * post a comment on pull requests that have
> > PatchCheck.py errors.
> > > +#
> > > +# Configuration Notes:
> > > +# * Update the 'base=edk2-ci' statements with the
> > name of the branch to merge
> > > +#   pull requests.
> > > +#
> > > +# * Update the 'status-failure' statement with the
> > name of the name of the Azure
> > > +#   Pipelines Build that performs the EDK II
> > Maintainer check.
> > > +#
> > > +# * 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>
> > > +# SPDX-License-Identifier: BSD-2-Clause-Patent
> > > +#
> > > +# https://github.com/apps/mergify
> > > +# https://doc.mergify.io/
> > > +#
> > > +##
> > > +
> > > +pull_request_rules:
> > > +
> > > +  - name: Automatically merge a PR when all required
> > checks pass and 'push' label is present
> > > +    conditions:
> > > +      - base=master
> > > +      - label=push
> > > +      - author=@tianocore/edk-ii-maintainers
> > > +      - status-success=tianocore.PatchCheck
> > > +      - status-success=Ubuntu GCC5 PR
> > > +      - status-success=Windows VS2019 PR
> > > +    actions:
> > > +      merge:
> > > +        strict: true
> > > +        method: rebase
> > > +
> > > +  - name: Automatically close a PR when all required
> > checks pass and 'push' label is not present
> > > +    conditions:
> > > +      - base=master
> > > +      - -label=push
> > > +      - -closed
> > > +      - status-success=tianocore.PatchCheck
> > > +      - status-success=Ubuntu GCC5 PR
> > > +      - status-success=Windows VS2019 PR
> > > +      - status-success=Ubuntu GCC5 PR (FINISHED)
> > > +      - status-success=Windows VS2019 PR (FINISHED)
> > > +    actions:
> > > +      close:
> > > +        message: All checks passed. Auto close
> > personal build.
> > > +
> > > +  - name: Post a comment on a PR that can not be
> > merged due to a merge conflict
> > > +    conditions:
> > > +      - base=master
> > > +      - conflict
> > > +    actions:
> > > +      comment:
> > > +        message: PR can not be merged due to
> > conflict.  Please rebase and resubmit
> > > +
> > > +  - name: Automatically close a PR that fails the
> > EDK II Maintainers membership check and 'push' label is
> > present
> > > +    conditions:
> > > +      - base=master
> > > +      - label=push
> > > +      - -author=@tianocore/edk-ii-maintainers
> > > +    actions:
> > > +      close:
> > > +        message: PR submitter is not a member of the
> > Tianocore EDK II Maintainers team
> > > +
> > > +  - name: Post a comment on a PR if PatchCheck fails
> > > +    conditions:
> > > +      - base=master
> > > +      - status-failure=tianocore.PatchCheck
> > > +    actions:
> > > +      comment:
> > > +        message: PR can not be merged due to a
> > PatchCheck failure.  Please resolve and resubmit
> > > +
> > > +  - name: Post a comment on a PR if Ubuntu GCC5
> > fails
> > > +    conditions:
> > > +      - base=master
> > > +      - status-failure=Ubuntu GCC5 PR
> > > +      - status-success=Ubuntu GCC5 PR (FAILED)
> > > +    actions:
> > > +      comment:
> > > +        message: PR can not be merged due to an
> > Ubuntu GCC5 failure.  Please resolve and resubmit
> > > +
> > > +  - name: Post a comment on a PR if Windows VS2019
> > fails
> > > +    conditions:
> > > +      - base=master
> > > +      - status-failure=Windows VS2019 PR
> > > +      - status-success=Windows VS2019 PR (FAILED)
> > > +    actions:
> > > +      comment:
> > > +        message: PR can not be merged due to a
> > Windows VS2019 failure.  Please resolve and resubmit
> > > --
> > > 2.21.0.windows.1
> > >
> > >
> > > 
> > >

  reply	other threads:[~2020-01-17 20:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  8:40 [Patch v5 00/22] Enable Phase 1 of EDK II CI Michael D Kinney
2019-11-11  8:40 ` [Patch v5 01/22] Maintainers.txt: Add continuous integration(CI) directories Michael D Kinney
2019-11-11  8:40 ` [Patch v5 02/22] .gitignore: Ignore python compiled files, extdeps, and vscode Michael D Kinney
2019-11-11  8:40 ` [Patch v5 03/22] pip_requirements.txt: Add python pip requirements file Michael D Kinney
2019-11-11  9:58   ` Laszlo Ersek
2019-11-11 16:35     ` Michael D Kinney
2019-11-11 16:41       ` Laszlo Ersek
2019-11-11  8:40 ` [Patch v5 04/22] BaseTools: Add RC_PATH define for VS2017/2019 Michael D Kinney
2019-11-11  8:40 ` [Patch v5 05/22] BaseTools: Add YAML files with path env and tool extdeps Michael D Kinney
2019-11-11  8:40 ` [Patch v5 06/22] BaseTools: Add BaseTools plugins to support CI Michael D Kinney
2019-11-11  8:40 ` [Patch v5 07/22] .pytool/Plugin: Add CI plugins Michael D Kinney
2019-11-11  8:40 ` [Patch v5 08/22] CryptoPkg: Add YAML file for CI builds Michael D Kinney
2019-11-11  8:40 ` [Patch v5 09/22] FatPkg: " Michael D Kinney
2019-11-11  8:40 ` [Patch v5 10/22] FmpDevicePkg: " Michael D Kinney
2019-11-11  8:40 ` [Patch v5 11/22] MdeModulePkg: " Michael D Kinney
2019-11-11  8:40 ` [Patch v5 12/22] MdePkg: " Michael D Kinney
2019-11-11  8:40 ` [Patch v5 13/22] NetworkPkg: " Michael D Kinney
2019-11-11  8:40 ` [Patch v5 14/22] PcAtChipsetPkg: Add YAML files " Michael D Kinney
2019-11-11  8:41 ` [Patch v5 15/22] SecurityPkg: " Michael D Kinney
2019-11-11  8:41 ` [Patch v5 16/22] ShellPkg: Add YAML file " Michael D Kinney
2019-11-11  8:41 ` [Patch v5 17/22] UefiCpuPkg: " Michael D Kinney
2019-11-11  8:41 ` [Patch v5 18/22] SignedCapsulePkg: Use BaseCryptLibNull to reduce package CI time Michael D Kinney
2019-11-11  8:41 ` [Patch v5 19/22] .pytool: Add CISettings.py and Readme.md Michael D Kinney
2019-11-11  8:41 ` [Patch v5 20/22] .azurepipelines: Add Azure Pipelines YML configuration files Michael D Kinney
2019-11-11  8:41 ` [Patch v5 21/22] .mergify: Add Mergify YML pull request rules configuration file Michael D Kinney
2020-01-17 19:44   ` [edk2-devel] " Leif Lindholm
2020-01-17 20:22     ` Michael D Kinney
2020-01-17 20:29       ` Leif Lindholm [this message]
2019-11-11  8:41 ` [Patch v5 22/22] Readme.md: Add CI build status badges Michael D Kinney
2019-11-11 17:14   ` Leif Lindholm

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=20200117202912.GO20629@bivouac.eciton.net \
    --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