From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.120])
 by mx.groups.io with SMTP id smtpd.web09.2123.1575630185603797704
 for <devel@edk2.groups.io>;
 Fri, 06 Dec 2019 03:03:05 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=RmG59IQy;
 spf=pass (domain: redhat.com, ip: 207.211.31.120, mailfrom: lersek@redhat.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
	s=mimecast20190719; t=1575630184;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=+Htcxr1xw2YlH3SpPy9QHe/+b72yIgMDh0WjFH5pY6c=;
	b=RmG59IQyCTtiEUpJ4dmQuuxsmnvT7hWYZ13OhLaiORZ1gFATEhq9aVCLqScQINe3geGK8X
	DslSU4QzxyBpwHtNkZelzp831629gSESRc+4HEkv4ssKcZLxs5VKYLZKlWPyKMQvps4YjO
	BdUsU3px6P015knXjR2H9coci5JkYTg=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-329--I9cTtj5PxqtbwR2ZBxbkQ-1; Fri, 06 Dec 2019 06:03:02 -0500
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EBB8C593A5;
	Fri,  6 Dec 2019 11:03:00 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-235.ams2.redhat.com [10.36.116.235])
	by smtp.corp.redhat.com (Postfix) with ESMTP id B305460138;
	Fri,  6 Dec 2019 11:02:59 +0000 (UTC)
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 <sean.brogan@microsoft.com>,
 Bret Barkelew <Bret.Barkelew@microsoft.com>,
 "Gao, Liming" <liming.gao@intel.com>
References: <E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORSMSX113.amr.corp.intel.com>
From: "Laszlo Ersek" <lersek@redhat.com>
Message-ID: <836dd53e-b8ad-17c2-f94d-c1756e715f50@redhat.com>
Date: Fri, 6 Dec 2019 12:02:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9E173A1@ORSMSX113.amr.corp.intel.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-MC-Unique: -I9cTtj5PxqtbwR2ZBxbkQ-1
X-Mimecast-Spam-Score: 0
Content-Language: en-US
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

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 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 don't know where I can file RFEs for the CI system.

For now, I've filed:

https://bugzilla.tianocore.org/show_bug.cgi?id=2406

The request is to allow subsystem maintainers to opt out of, or waive,
PatchCheck.py failures. The commit message line length checks in
PatchCheck.py make sense as a default, but there are valid cases when
they should be turned off. Please see details in the BZ.

Thanks!
Laszlo