<p><a class="user-mention" data-hovercard-user-id="1223908" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Emzy">@Emzy</a>, I noticed after the fact that you did actually do a monthly Pricenode Operator report at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="255026715" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/roles/issues/14" href="https://github.com/bisq-network/roles/issues/14#issuecomment-386404037">bisq-network/roles#14 (comment)</a>. Thanks. If in the future, you backreference your compensation requests from your role report comments, e.g. with a <code>/cc bisq-network/compensation#64</code>, it'll ensure that everything is discoverable in a bi-directional way. You can see this in effect in my compensation requests, e.g. this month's at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="319495705" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/compensation/issues/68" href="https://github.com/bisq-network/compensation/issues/68">#68</a>. Scroll to the bottom and you'll see the back-references in the issue timeline coming in from the individual role report comments.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/compensation/issues/64#issuecomment-387367265">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZthqrf-GSYbEV9-hdXgTPXq--Cv1lks5twXxPgaJpZM4Tt0tR">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtmhYmF8wAobH4Ez3Wc5TXv21-OVQks5twXxPgaJpZM4Tt0tR.gif" height="1" width="1" alt="" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/bisq-network/compensation/issues/64#issuecomment-387367265"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/compensation","title":"bisq-network/compensation","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/compensation"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams in #64: @Emzy, I noticed after the fact that you did actually do a monthly Pricenode Operator report at https://github.com/bisq-network/roles/issues/14#issuecomment-386404037. Thanks. If in the future, you backreference your compensation requests from your role report comments, e.g. with a `/cc bisq-network/compensation#64`, it'll ensure that everything is discoverable in a bi-directional way. You can see this in effect in my compensation requests, e.g. this month's at https://github.com/bisq-network/compensation/issues/68. Scroll to the bottom and you'll see the back-references in the issue timeline coming in from the individual role report comments."}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/compensation/issues/64#issuecomment-387367265"}}}</script>