# 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:** 3

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [June 30, 2016, 5:41pm UTC](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671/3 "2016-06-30T17:41:10Z")

</div>

The most common use case is when an issue tracker gets overburdened with “Discussion” and “Enhancement” issues. [Atom.io](http://Atom.io) provides a very relevant case study:

> **[Sunsetting Atom](https://github.blog/news-insights/product-news/sunsetting-atom/)**
>
> We are archiving Atom and all projects under the Atom organization for an official sunset on December 15, 2022.

---

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