From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web12.12392.1577976128940013302 for ; Thu, 02 Jan 2020 06:42:09 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aWygosQ6; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: philmd@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1577976128; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iJDN9zCRDLtB1mT3+0a6rexV31hsDwxzQFaMF6C+hRo=; b=aWygosQ6jy13CvBi6zBle6/8nGv0hBRrnZC+XLiAtFq0Pl22JEVYcCoghvfCgQAsB1HHVt pkSw0bhEPwLrHwfEMangm+KvIEqfJW4dKLnjIzVzKDuTqi0wpqOrI8DHvV7xrJyAl5cKgA hz/9Lldu2spwJBAkSLM/XlPOy2IEcMg= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-331-TK5UofD6NBaraQO4e4IvjQ-1; Thu, 02 Jan 2020 09:42:06 -0500 Received: by mail-ed1-f71.google.com with SMTP id g20so16013661edt.18 for ; Thu, 02 Jan 2020 06:42:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:cc:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iJDN9zCRDLtB1mT3+0a6rexV31hsDwxzQFaMF6C+hRo=; b=CDwv0RjEO2K3QC/nYkBPg75Zmq5kcp+0N18YMitnl6RYasAI+0LCkE6B4X4DrJcXj4 UtEM0+9EbRqrPHTEqnFGqTrrynJ4KAWEFJmpMrJxvRlOKuj08i1zK7Sd2uWZQxicBNnf 2ojLyz5u8bCg6aPxYTvqFWYg+jYU73YWqmPPds9+LZfMFhCUfWDv3/y8a98o/moAxPvU rC3dxp6IKQJfa1o8buDSJovIoKtIqS6gS9C6ijcuazMyBus1acbh3J6s3k+pRm2e5Z3c ekSeXIKKQKIsJYelSOBRo4Wp2j0CEFrFC21EmlrscRGqj87UTsFc29okcL87SQOQdJGB 4Zmg== X-Gm-Message-State: APjAAAX0eJel6wW878i3Yw3CHu5Cm+i5X64lZsxO98tTFcpNh0H3/XrS +UwffPSVRv2yzx0XY7lZ4KgFqESxE/u38wVQwDUgwFgy6v52cB77FWxfWJ1D39Q5UqkPjJaPAcK NGFwMhvXaU8XT3Q== X-Received: by 2002:a17:907:40bb:: with SMTP id nu19mr64083879ejb.145.1577976124762; Thu, 02 Jan 2020 06:42:04 -0800 (PST) X-Google-Smtp-Source: APXvYqwemB43FF648sJ5JOUAY4vZ8X7u9MK1RAVtpMj85z4dXgsN5g3gzfedvr43Cvh9FvWeGMOnZA== X-Received: by 2002:a17:907:40bb:: with SMTP id nu19mr64083857ejb.145.1577976124498; Thu, 02 Jan 2020 06:42:04 -0800 (PST) Return-Path: Received: from [192.168.50.32] (243.red-88-26-246.staticip.rima-tde.net. [88.26.246.243]) by smtp.gmail.com with ESMTPSA id x2sm6737799edi.95.2020.01.02.06.42.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 Jan 2020 06:42:03 -0800 (PST) Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master To: devel@edk2.groups.io, michael.d.kinney@intel.com, Sean Brogan , Bret Barkelew , "Gao, Liming" References: From: =?UTF-8?B?UGhpbGlwcGUgTWF0aGlldS1EYXVkw6k=?= Cc: Laszlo Ersek Message-ID: Date: Thu, 2 Jan 2020 15:42:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: X-MC-Unique: TK5UofD6NBaraQO4e4IvjQ-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 edk2/master. The GitHub PR > replaces the 'git push' operation currently used to commit > changes to edk2/master. > > You will need to configure your notifications from the edk2 > repository to make sure you receive email notifications > when the checks against the GitHub PR passes or fails. > > If you submit a GitHub Pull Request without the 'push' > label, then the CI checks are run and the results are > generated. > > Please let us know if there are any questions about this > change in the development process. I have 2 requests: 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? Before we could directly use this information to email the maintainer who merged the patch in. Currently I can't find an easy way... I've to dig thru the mailing list archives for the last thread, figure out who could have merge this, check the different maintainers GitHub repository... The new way might be using this filter (which is not listed by default): https://github.com/tianocore/edk2/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged Then go thru the last ones, but this doesn't scale in few months to look at old merges. 2/ Can the Mergify bot send a mail to the list to notify a patch got merged? For example going thru my backlog I was going to review this series: https://edk2.groups.io/g/devel/message/52613 But it is already merged... The series subject is "Microcode related optimizations" and when I searched for it first with the GitHub MR filter from 1/, I couldn't find it. Later I figured it got merged with another subject "Mpinitlib opt push 1". One way to simplify Mergify to send email, is to ask maintainers to put the series cover (or each patches) URL in the GitHub merge request description, or the email Message ID(s). Since we are switching the a mostly HTTP workflow, using URLs is probably recommended. Thanks, and happy new year! :) Phil.