# Introducing GitHub Issues to Discourse

**URL:** <https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671>\
**Category:** Extras\
**Created:** [June 30, 2016, 4:18pm UTC](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671 "2016-06-30T16:18:49Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Robert\_Lee\_Louviere](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Robert\_Lee\_Louviere](https://meta.discourse.org/u/Robert_Lee_Louviere)\
**Post date:** [July 5, 2016, 8:38pm UTC](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671/11 "2016-07-05T20:38:19Z")

</div>

Ok, so you have a few options.

1. Lock the GitHub ticket. Lose the ability to ask for pertinent additional information unless you unlock the thread.
2. Do the OP suggestion. Leave the GitHub open. The conversation splits and bike-shedding happens on the ticket anyway.
3. Do the OP suggestion. Lock the GitHub thread. Sort through all the bikeshedding on here for pertinent information, pushing the problem back 1 step to obscurity.
4. OR the MOST LIKELY THING. Do the OP suggestion. Lock the GitHub thread. Ignore any further pertinent information on Discourse because you put a barrier up to it.

Either way you’ll have to moderate. So, why not keep the conversation on GitHub and moderate it there. If you have to lock the thread, someone can PM you here and you can post it on that thread.

---

_[View the full topic](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671)._