I would also hope that most (if not all) patches do have an associated BZ. For either a feature request or a bug fix.
Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] > On Behalf Of stephano > Sent: Thursday, October 18, 2018 10:21 AM > To: Andrew Fish <af...@apple.com> > Cc: Carsey, Jaben <jaben.car...@intel.com>; edk2- > de...@lists.01.org > Subject: Re: [edk2] Community Discussion: General Code > and Commit message standards > > 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-<Bugzilla #>-<discription>. > 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. > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
