<div dir="ltr"><div>Thanks all!</div><div><br></div>Looks like the ability to associate comes after submitting the pull request: I submitted one, and then was able to have it associate. That's not at all clear in the docs. :)<div><br></div><div>I don't know for sure if I can say that something closes something yet, given it's my first bug on this project?</div><div><br></div><div>Sz</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 12:46 PM, Leslie Hinson <span dir="ltr"><<a href="mailto:lhinson@redhat.com" target="_blank">lhinson@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Nice, tip Jonathan. I did know this one. <span class="HOEnZb"><font color="#888888"><div><br></div><div>Leslie</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 11:08 AM, Jonathan Yu <span dir="ltr"><<a href="mailto:jawnsy@redhat.com" target="_blank">jawnsy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">It's also beneficial to use "Closes: #111" as it will automatically close the associated issue once the PR is merged, if the PR is intended to fix an issue. There's an explanation of this here: <a href="https://help.github.com/articles/closing-issues-via-commit-messages/" target="_blank">https://help.github.com/articl<wbr>es/closing-issues-via-commit-<wbr>messages/</a><div><div class="m_-3637520881070991533h5"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 5:39 AM, Leslie Hinson <span dir="ltr"><<a href="mailto:lhinson@redhat.com" target="_blank">lhinson@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Exactly. Thanks Chris! <span class="m_-3637520881070991533m_2900875174049975802HOEnZb"><font color="#888888"><div><br></div><div>Leslie</div></font></span></div><div class="m_-3637520881070991533m_2900875174049975802HOEnZb"><div class="m_-3637520881070991533m_2900875174049975802h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 5, 2017 at 8:10 AM, Chris Shinn <span dir="ltr"><<a href="mailto:cshinn@redhat.com" target="_blank">cshinn@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Hi Suzanne,</div><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">When making a comment or editing an existing one, type # and you should get a list of open Pull Requests (PRs) and bugs that you can select from, or you can simply type # followed by the number of the bug or PR. That will associate it and add a note.</div><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Best,</div><div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Chris</div><div><div class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115h5"> <br> <div id="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_sign_1491394027565280000" class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802bloop_sign"></div> <br><p class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802airmail_on">On April 4, 2017 at 5:23:08 PM, Suzanne Hillman (<a href="mailto:wispfox@gmail.com" target="_blank">wispfox@gmail.com</a>) wrote:</p> <blockquote type="cite" class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802clean_bq"><span><div><div></div><div>





<div dir="ltr">Hi Leslie!
<div><br></div>
<div>How do I associate a change I made in response to a bug with
the bug itself? Eg: <a href="https://github.com/patternfly/patternfly-design/issues/240" target="_blank">https://github.com/pattern<wbr>fly/patternfly-design/issues/2<wbr>40</a>
and the pull request step in <a href="https://github.com/patternfly/patternfly-design/wiki/Contribution-Workflow" target="_blank">https://github.com/patternf<wbr>ly/patternfly-design/wiki/Cont<wbr>ribution-Workflow</a></div>
<div><br></div>
<div>I can't tell if I'm missing something here!</div>
<div><br></div>
<div>Thanks,</div>
<div><br></div>
<div>Suzanne</div>
<div><br></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Apr 3, 2017 at 3:09 PM, Leslie
Hinson <span dir="ltr"><<a href="mailto:lhinson@redhat.com" target="_blank">lhinson@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hey Suzanne!
<div><br></div>
<div>
<div>Excited to see you getting involved with PatternFly
design. </div>
<div><br></div>
<div>I would suggest taking a look at our design repo seen
here: <a href="https://github.com/patternfly/patternfly-design" target="_blank">https://github.com/patte<wbr>rnfly/patternfly-design</a>.
The repo is where we manage and maintain all of our design
documentation for <a href="http://patternfly.org" target="_blank">patternfly.org</a>. </div>
<div><br></div>
<div>Also, check out the "contribution guides" section (<a href="https://github.com/patternfly/patternfly-design/wiki#contribution-guides" target="_blank">https://github.com/patternfly<wbr>/patternfly-design/wiki#contri<wbr>bution-guides</a>)
to learn how to get setup and contribute. </div>
<div><br></div>
<div>If you are interested, you can pick up an issue here: <a href="https://github.com/patternfly/patternfly-design/issues" target="_blank">https://github.com/patternfly/<wbr>patternfly-design/issues</a>
called "easy fix". This will help you get some experience going
through our PR process. <br></div>
<div><br></div>
<div>Let's start here but let us know if you have any
questions! </div>
</div>
<div><br></div>
<div>Best, </div>
<div>Leslie</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">
<div>
<div class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802h5">On Mon, Apr 3, 2017 at 2:42 PM, Jonathan Yu
<span dir="ltr"><<a href="mailto:jawnsy@redhat.com" target="_blank">jawnsy@redhat.com</a>></span> wrote:<br></div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802h5">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span>On Mon, Apr 3, 2017 at 11:05 AM,
Suzanne Hillman <span dir="ltr"><<a href="mailto:wispfox@gmail.com" target="_blank">wispfox@gmail.com</a>></span> wrote:<br></span>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div dir="ltr">Hi,
<div><br></div>
<div>I'm hoping to get involved in patternfly, but found the
public-facing jira page rather opaque.</div>
</div>
</blockquote>
<div><br></div>
<div>Sorry to hear that - hopefully we can use your feedback to
improve the experience :)<br>
<br></div>
<div>I suggest joining our Slack channel; you can get an invite
from <a href="http://slack.patternfly.org" target="_blank">http://slack.patternfly.org</a><br></div>
<div><span> <br></span></div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div dir="ltr">
<div><span>I was wondering if there were any specific aspects that
need more UX eyes or suggestions or ideas.</span></div>
<div><span><br></span></div>
<div><span>I've got a lot of experience working with Linux,
primarily as QE, and have just finished a UX internship with Fedora
through Outreachy. I'm hoping to get more involved in UX in the
open source space.</span></div>
</div>
</blockquote>
<div><span><br></span></div>
<div>Sweet, welcome! I think you'll find that the PatternFly team
is really welcoming and always willing to help. Sorry that I don't
really have any concrete suggestions (I'm mostly a PatternFly user,
and not part of the core team) but someone else should be around
with better advice shortly :)<span class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802m_2004474630762683180HOEnZb"><font color="#888888"><br></font></span></div>
<span class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802m_2004474630762683180HOEnZb"><font color="#888888"><br></font></span></div>
<span class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802m_2004474630762683180HOEnZb"><font color="#888888">--<br></font></span>
<div class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802m_2004474630762683180m_-7153879072684651545gmail_signature">
<div dir="ltr">
<div style="font-family:arial,"helvetica neue",helvetica,sans-serif;font-size:9pt;line-height:11pt;color:rgb(85,85,85)">
<div><span class="m_-3637520881070991533m_2900875174049975802m_-5508989971228990115m_-4924967505881998802m_2004474630762683180HOEnZb"><font color="#888888"><span><span>Jonathan</span> <span>Yu</span></span> /
<span>Software Engineer</span>, <span>OpenShift</span> by <span>Red
Hat</span> / <a style="color:rgb(63,184,175);text-decoration:none" href="https://twitter.com/jawnsy" target="_blank">@jawnsy</a></font></span></div>
<br>
<i>“There are a million ways to get rich. But there’s only one way
to stay rich: Humility, often to the point of paranoia. The irony
is that few things squash humility like getting rich in the first
place.”</i> — Morgan Housel, <a style="color:rgb(63,184,175);text-decoration:none" href="http://www.collaborativefund.com/blog/getting-rich-vs-staying-rich/" target="_blank">Getting Rich vs. Staying Rich</a></div>
</div>
</div>
</div>
</div>
<br></div>
</div>
______________________________<wbr>_________________<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<wbr>/listinfo/patternfly</a><br>

<br></blockquote>
</div>
<br></div>
</blockquote>
</div>
<br></div>


______________________________<wbr>_________________
<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" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/patternfly</a>
<br></div></div></span></blockquote></div></div></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<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<wbr>/listinfo/patternfly</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="m_-3637520881070991533m_2900875174049975802gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">
        <div style="font-family:Arial,'Helvetica Neue',Helvetica,sans-serif;font-size:9pt;line-height:11pt;color:#555">
            <div>
                <span>
                    <span>Jonathan</span>
                    <span>Yu</span>
                </span>
                /
                <span>Software Engineer</span>, <span>OpenShift</span> by <span>Red Hat</span>
                /
                <a href="https://twitter.com/jawnsy" style="color:#3fb8af;text-decoration:none" target="_blank">@jawnsy</a>
            </div>
            <br>
            <i>“There are a million ways to get rich. But there’s only 
one way to stay rich: Humility, often to the point of paranoia. The 
irony is that few things squash humility like getting rich in the first 
place.”</i> — Morgan Housel, <a href="http://www.collaborativefund.com/blog/getting-rich-vs-staying-rich/" style="color:#3fb8af;text-decoration:none" target="_blank">Getting Rich vs. Staying Rich</a>
        </div>
    

</div></div>
</div></div></div></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
PatternFly mailing list<br>
<a href="mailto:PatternFly@redhat.com">PatternFly@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/patternfly" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/patternfly</a><br>
<br></blockquote></div><br></div>