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.81]) by mx.groups.io with SMTP id smtpd.web09.6850.1578331771483081882 for ; Mon, 06 Jan 2020 09:29:31 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=grluM8gI; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578331770; 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=xWWUNLv0MVYqzMTgR4PRd5L3Ohf34Ju/ME1nvbMu17A=; b=grluM8gI2dDJfXnfojaLkuN1qC1TcLoG78fosyZKUptcIMEFxqZkXFYu/7aG+BL1wUJFDi qtLjZNAJXMus+lgxqJvpRrfPpIUdQsWOHigyBNSk1Lp51VT7SjGfkNkz0JC+S4qixraqBM flwQVAK73X+vbBzrKdfxUeAyIs+Cifw= 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-7-eeyaMY42NcSIpWAQDZbP2Q-1; Mon, 06 Jan 2020 12:29:27 -0500 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DEF1C10946E3; Mon, 6 Jan 2020 17:29:25 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-117-24.ams2.redhat.com [10.36.117.24]) by smtp.corp.redhat.com (Postfix) with ESMTP id A8A94858AB; Mon, 6 Jan 2020 17:29:24 +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 , Bret Barkelew , "Gao, Liming" References: From: "Laszlo Ersek" Message-ID: <1443759e-a8a1-2c5f-4892-0ff740e948ba@redhat.com> Date: Mon, 6 Jan 2020 18:29:23 +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: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-MC-Unique: eeyaMY42NcSIpWAQDZbP2Q-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 had filed https://bugzilla.tianocore.org/show_bug.cgi?id=2406 a month ago, about PatchCheck.py being too strict, and blocking pull requests unjustifiedly. Now I realize I can't even review the results (= the PatchCheck.py error messages) on github.com and/or on Azure Pipelines: https://github.com/tianocore/edk2/pull/272/checks?check_run_id=375969977 https://dev.azure.com/tianocore/11ea4a10-ac9f-4e5f-8b13-7def1f19d478/_build/results?buildId=3456 Am I looking in the wrong place perhaps? Can we please add a manual PatchCheck.py override on github.com for those maintainers that are permitted to set the "push" label already? TianoCore#2406 doesn't seem to be getting any attention, and it is blocking actual development work. Thanks Laszlo