From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=192.55.52.151; helo=mga17.intel.com; envelope-from=stephano.cetola@linux.intel.com; receiver=edk2-devel@lists.01.org Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 71A662194D387 for ; Thu, 18 Oct 2018 10:21:17 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2018 10:21:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,397,1534834800"; d="scan'208";a="89372213" Received: from scetola-mobl1.amr.corp.intel.com (HELO [10.252.17.151]) ([10.252.17.151]) by FMSMGA003.fm.intel.com with ESMTP; 18 Oct 2018 10:21:15 -0700 To: Andrew Fish Cc: "Carsey, Jaben" , "edk2-devel@lists.01.org" References: <8dd58f85-3836-4951-3efe-f4c0aef7a1a1@linux.intel.com> <3ADBB72A-4190-4D58-A359-E493BB1A65CB@apple.com> <18984317-b515-9788-0495-af2b0b698ba9@linux.intel.com> <7D30FC28-2AE8-48F9-8942-8D5593E009DA@apple.com> From: stephano Message-ID: <5bfbdb37-54c4-b8a0-9281-ef56d9327ae9@linux.intel.com> Date: Thu, 18 Oct 2018 18:21:14 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <7D30FC28-2AE8-48F9-8942-8D5593E009DA@apple.com> Subject: Re: Community Discussion: General Code and Commit message standards X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Oct 2018 17:21:17 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit On 10/18/2018 6:11 PM, Andrew Fish wrote:> What I've done in the past on a branch based github PR flow is have a naming convention for the branch. For example eng/PR--. Then we have a git hook that looks at the branch name and if it sees a Bugzilla number it inserts the Bugzilla reference in the bottom of every commit message for that branch. The CI also played tricks with the branch names and could update the bug tracker with CI results, and the process status of the bug. Interesting. This will make a good point for coming discussions. I'll make a note of it. I would hope that most modern workflows have a way to accomplish this in some automated way. Seems like a pretty standard ask.