From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.120]) by mx.groups.io with SMTP id smtpd.web10.1417.1573631793984999175 for ; Tue, 12 Nov 2019 23:56:34 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VU1vOS9f; spf=pass (domain: redhat.com, ip: 205.139.110.120, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573631793; 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=HxOKII8FXW9AK7w7nHQI1M8ZfMVYN8NOX05rii6zA00=; b=VU1vOS9fxXR8A8j47Cknv5fFHt9WHwB3cznRNTCVPC2LIUf2cciC30hx5sUJMvV/ZyMYDD PkFB8rjuhDeReUbVmSWs2jASf0Wg74b1jPQxYWZcUK9jKuSyOa5srSU5y+i3nnWzY0zNXs Od6EwAVzAXKmduKPo3k37aBKG8YLBbM= 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-314-TiqIE3MEO-ODwUw0fdnGzg-1; Wed, 13 Nov 2019 02:56:29 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 74D97107B291; Wed, 13 Nov 2019 07:56:28 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-243.ams2.redhat.com [10.36.116.243]) by smtp.corp.redhat.com (Postfix) with ESMTP id 25D6963643; Wed, 13 Nov 2019 07:56:26 +0000 (UTC) Subject: Re: [edk2-devel] EDK II Maintainers - EDK II CI is now active on edk2/master To: "Kinney, Michael D" , "devel@edk2.groups.io" , Sean Brogan , Bret Barkelew , "Gao, Liming" References: <888e1c71-d558-0afa-1dc7-cfead9717294@redhat.com> From: "Laszlo Ersek" Message-ID: <4ce78c14-57f8-f6f3-e542-f5e09cd951ce@redhat.com> Date: Wed, 13 Nov 2019 08:56:26 +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.15 X-MC-Unique: TiqIE3MEO-ODwUw0fdnGzg-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable On 11/12/19 20:50, Kinney, Michael D wrote: > Hi Laszlo, >=20 > The setting that is required is 'Watch' on the edk2 repo. > Navigate to the main page for the tianocore edk2 repo: >=20 > https://github.com/tianocore/edk2 >=20 > At the top of the page, there is a drop down called 'Watch'. > Select 'Watching - Be notified of all conversations.' Thank you; it looks like I had this set already. (I sort of suspected that, but wanted to make sure I had the right config in place.) Cheers! Laszlo > GitHub documentation on this feature: >=20 > https://help.github.com/en/github/receiving-notifications-about-activity= -on-github/about-notifications#watching-notifications >=20 > Best regards, >=20 > Mike >=20 >> -----Original Message----- >> From: Laszlo Ersek >> Sent: Tuesday, November 12, 2019 12:56 AM >> To: devel@edk2.groups.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, >>> >>> 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 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. >> >> Can you please provide instructions for reaching those >> notification settings? >> >> (If there is a single "settings" URL that I have to >> open in my browser, while being logged in to my GitHub >> account, then sharing that URL here would be ideal.) >> >> Thanks! >> Laszlo >> >>> >>> 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. >>> >>> Best regards, >>> >>> Mike >>> >>>=20 >>> >=20