From: stephano <stephano.cetola@linux.intel.com>
To: Andrew Fish <afish@apple.com>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Community Discussion: General Code and Commit message standards
Date: Thu, 18 Oct 2018 18:21:14 +0100 [thread overview]
Message-ID: <5bfbdb37-54c4-b8a0-9281-ef56d9327ae9@linux.intel.com> (raw)
In-Reply-To: <7D30FC28-2AE8-48F9-8942-8D5593E009DA@apple.com>
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.
next prev parent reply other threads:[~2018-10-18 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 9:12 Community Discussion: General Code and Commit message standards stephano
2018-10-18 14:22 ` Carsey, Jaben
2018-10-18 15:49 ` Andrew Fish
2018-10-18 16:43 ` stephano
2018-10-18 17:11 ` Andrew Fish
2018-10-18 17:21 ` stephano [this message]
2018-10-18 23:01 ` Kinney, Michael D
2018-10-19 16:21 ` Jeremiah Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bfbdb37-54c4-b8a0-9281-ef56d9327ae9@linux.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox