<div dir="ltr">+1 <div><br></div><div>Sorry Dan, we've been writing poor PR descriptions.<div><br></div><div>Here is a guide useful <a href="https://github.com/blog/1943-how-to-write-the-perfect-pull-request">https://github.com/blog/1943-how-to-write-the-perfect-pull-request</a></div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 6, 2016 at 10:30 AM, Dan Labrecque <span dir="ltr"><<a href="mailto:dlabrecq@redhat.com" target="_blank">dlabrecq@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Please add descriptive comments when creating PRs as we refer back to this when creating release notes. The latest PRs are completely missing descriptions and the commit comments are vague -- sometimes, only a story number is available in the commit message. It's difficult to understand what is a new feature Vs enhancement, bug fix, etc.<br>
<br>
Thanks,<br>
<br>
Dan<br>
<br>
<br>
_______________________________________________<br>
Patternfly mailing list<br>
<a href="mailto:Patternfly@redhat.com" target="_blank">Patternfly@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/patternfly" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/patternfly</a><br>
</blockquote></div><br></div>