On 03/09/20 22:44, Kinney, Michael D wrote:
> Laszlo,
>
> If the dev branch that is being submitted as a PR
> contains the merge commit, or that developer use the
> one of the github features to rebase, the merge
> commit can be introduced.
>
> When a PR is in this state, the developer need to
>
020 12:32 PM
> To: Kinney, Michael D ;
> devel@edk2.groups.io; sean.bro...@microsoft.com; Bret
> Barkelew ; Gao, Liming
>
> Cc: Leif Lindholm (Nuvia address) ;
> Andrew Fish
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> On
osoft.com; Bret
> Barkelew ; Gao, Liming
>
> Cc: Leif Lindholm (Nuvia address) ;
> Andrew Fish
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Hello again,
>
> On 03/08/20 20:53, Kinney, Michael D wrote:
>
> > This
Hello again,
On 03/08/20 20:53, Kinney, Michael D wrote:
> This one is failing PatchCheck with a missing Signed-off-by
> https://github.com/tianocore/edk2/pull/430
The lack of signed-off-by is a red herring.
Ard's pull request
https://github.com/tianocore/edk2/pull/430
consists of
On 03/09/20 20:29, Laszlo Ersek wrote:
> mergify.io didn't respond to my ticket
They have gotten back to me since; quote:
On 03/09/20 14:10, Mehdi Abaakouk wrote:
> We are aware of the issue and working on a fix. We recently implement
> a Github recommendation about caching Github API HTTP
On 03/09/20 20:29, Laszlo Ersek wrote:
> Hi Mike,
>
> On 03/08/20 20:53, Kinney, Michael D wrote:
>> I added the @Mergifyio refresh to these PRs.
>>
>> This one was merged:
>> https://github.com/tianocore/edk2/pull/427
>>
>> This one is failing PatchCheck with a missing Signed-off-by
>>
Hi Mike,
On 03/08/20 20:53, Kinney, Michael D wrote:
> I added the @Mergifyio refresh to these PRs.
>
> This one was merged:
> https://github.com/tianocore/edk2/pull/427
>
> This one is failing PatchCheck with a missing Signed-off-by
> https://github.com/tianocore/edk2/pull/430
>
>
ng
> ; Kinney, Michael D
>
> Cc: Leif Lindholm (Nuvia address) ;
> Andrew Fish
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Laszlo - Added comment to your PR.
> @Mike Kinney (michael.d.kin...@intel.com) who has
> mergi
gan ; Bret Barkelew
; Gao, Liming
Cc: Leif Lindholm (Nuvia address) ; Andrew Fish
Subject: [EXTERNAL] Re: [edk2-devel] EDK II Maintainers - EDK II CI is now
active on edk2/master
On 11/12/19 03:55, Michael D Kinney wrote:
> Please let us know if there are any questions about this change in the
On 11/12/19 03:55, Michael D Kinney wrote:
> Please let us know if there are any questions about this
> change in the development process.
What is the recommended way to report issues with the mergify (not CI)
infrastructure?
Mergify hasn't been picking up ready-to-merge branches (with CI
t;> Sent: Thursday, January 9, 2020 1:31 PM
>> To: Kinney, Michael D ;
>> devel@edk2.groups.io; Sean Brogan
>> ; Bret Barkelew
>> ; Gao, Liming
>>
>> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
>> CI is now active on edk2/master
>>
>
2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Hi Mike,
>
> On 01/06/20 19:17, Kinney, Michael D wrote:
> > Laszlo,
> >
> > Sorry for the delay in getting to these
> PactchCheck.py updates.
> > I know it is frustrating to be block
Hi Mike,
On 01/06/20 19:17, Kinney, Michael D wrote:
> Laszlo,
>
> Sorry for the delay in getting to these PactchCheck.py updates.
> I know it is frustrating to be blocked by these types of issues.
> I try to look at 2406 tomorrow. I think the manual override is
> potentially more complex to
Hello Mike,
On 01/06/20 19:17, Kinney, Michael D wrote:
> Laszlo,
>
> Sorry for the delay in getting to these PactchCheck.py updates.
> I know it is frustrating to be blocked by these types of issues.
> I try to look at 2406 tomorrow.
Thanks!
> I think the manual override is
> potentially more
g
>
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Hi Mike,
>
> On 11/12/19 03:55, Michael D Kinney wrote:
> > EDK II Maintainers,
> >
> > EDK II CI Phase 1 feature is now active on
> edk2/master.
> &
Hi Mike,
On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
>
> EDK II CI Phase 1 feature is now active on edk2/master.
>
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be pushed to
.
-Original Message-
From: devel@edk2.groups.io On
Behalf Of Philippe Mathieu-Daudé
Sent: Thursday, January 2, 2020 6:42 AM
To: devel@edk2.groups.io; Kinney, Michael D
; Sean Brogan
; Bret Barkelew
; Gao, Liming
Cc: Laszlo Ersek
Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
CI
On 01/02/20 15:42, Philippe Mathieu-Daudé wrote:
> 1/ Is it possible to have the Mergify bot use the merge request author
> name/email as GIT_COMMITTER_[NAME/EMAIL] instead of throwing away this
> information from the git history?
I noticed that too, but I thought that having a robot rather than
nal Message-
> From: devel@edk2.groups.io On
> Behalf Of Philippe Mathieu-Daudé
> Sent: Thursday, January 2, 2020 6:42 AM
> To: devel@edk2.groups.io; Kinney, Michael D
> ; Sean Brogan
> ; Bret Barkelew
> ; Gao, Liming
>
> Cc: Laszlo Ersek
> Subject: Re: [edk2-d
Hi Michael,
On 11/12/19 3:55 AM, Michael D Kinney wrote:
EDK II Maintainers,
EDK II CI Phase 1 feature is now active on edk2/master.
Please use a GitHub pull request from a branch in a personal
fork of the edk2 repository with a 'push' label to request
a set of patches to be pushed to
On 12/06/19 12:02, Laszlo Ersek wrote:
> Hi Mike,
>
> On 11/12/19 03:55, Michael D Kinney wrote:
>> EDK II Maintainers,
>>
>> EDK II CI Phase 1 feature is now active on edk2/master.
>>
>> Please use a GitHub pull request from a branch in a personal
>> fork of the edk2 repository with a 'push'
Hi Mike,
On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
>
> EDK II CI Phase 1 feature is now active on edk2/master.
>
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be pushed to
On 12/03/19 18:07, Kinney, Michael D wrote:
> Hi Laszlo,
>
> I can think of ways we may be able to get the label
> information into the body of the email in a PR comment.
> I will have to see if there is anyway to adjust the subject
> of the email. The subject appears to always match the title
ecember 3, 2019 12:56 AM
> To: Kinney, Michael D ;
> devel@edk2.groups.io; Sean Brogan
> ; Bret Barkelew
> ; Gao, Liming
>
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> On 12/02/19 20:55, Kinney, Michael D wrote:
>
On 12/02/19 20:55, Kinney, Michael D wrote:
> So my question still stands. What notifications would
> you like to see if we have the use case of a single PR
> with multiple rounds of reviews and a transition from
> a PR without the 'push' label to a PR with a 'push' label?
Thank you for
Hi Laszlo,
Comments below.
Mike
> -Original Message-
> From: Laszlo Ersek
> Sent: Thursday, November 28, 2019 4:01 AM
> To: Kinney, Michael D ;
> devel@edk2.groups.io; Sean Brogan
> ; Bret Barkelew
> ; Gao, Liming
>
> Subject: Re: [edk2-devel] EDK II Maint
On 11/27/19 20:03, Kinney, Michael D wrote:
> Hi Laszlo,
>
> Do you want to see the presence of the 'push' label
> in a notification when the PR is created, or just
> when the checks have been completed in either the
> pass or the fail state?
I'd like to see the purpose of the PR in the first
Hi Mike,
On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
>
> EDK II CI Phase 1 feature is now active on edk2/master.
>
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be pushed to
e BZ comment (commit range and PR link).
Thank you!
Laszlo
>> -Original Message-
>> From: Laszlo Ersek
>> Sent: Wednesday, November 13, 2019 12:57 AM
>> To: devel@edk2.groups.io; Kinney, Michael D
>> ; Sean Brogan
>> ; Bret Barkelew
>> ; Gao, L
ay
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Hi again,
>
> (+Ray)
>
> On 11/12/19 03:55, Michael D Kinney wrote:
> > EDK II Maintainers,
> >
> > EDK II CI Phase 1 feature is now active on
>
Hi again,
(+Ray)
On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
>
> EDK II CI Phase 1 feature is now active on edk2/master.
>
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be
.io; Kinney, Michael D
>> ; Sean Brogan
>> ; Bret Barkelew
>> ; Gao, Liming
>>
>> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
>> CI is now active on edk2/master
>>
>> On 11/12/19 03:55, Michael D Kinney wrote:
>>> EDK II Maintainers
; To: Laszlo Ersek ;
> devel@edk2.groups.io; Sean Brogan
> ; Bret Barkelew
> ; Gao, Liming
> ; Kinney, Michael D
>
> Subject: RE: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> Hi Laszlo,
>
> The setting that is required is 'Watc
s.io; Kinney, Michael D
> ; Sean Brogan
> ; Bret Barkelew
> ; Gao, Liming
>
> Subject: Re: [edk2-devel] EDK II Maintainers - EDK II
> CI is now active on edk2/master
>
> On 11/12/19 03:55, Michael D Kinney wrote:
> > EDK II Maintainers,
> >
> > ED
On 11/12/19 03:55, Michael D Kinney wrote:
> EDK II Maintainers,
>
> EDK II CI Phase 1 feature is now active on edk2/master.
Awesome!
>
> Please use a GitHub pull request from a branch in a personal
> fork of the edk2 repository with a 'push' label to request
> a set of patches to be pushed to
EDK II Maintainers,
EDK II CI Phase 1 feature is now active on edk2/master.
Please use a GitHub pull request from a branch in a personal
fork of the edk2 repository with a 'push' label to request
a set of patches to be pushed to edk2/master. The GitHub PR
replaces the 'git push' operation
36 matches
Mail list logo
