Hi @tobiaseigen—thanks for your response. I’m not an administrator on any Discourse forums, and my suggestion is mainly based on a recurring experience I’ve had as a user and sometimes contributor on a variety of projects.
The reason I picked out Discourse Code Review is that it seems to be de facto the sole Discourse GitHub integration, unless there are other currently maintained projects I’m not aware of. Regardless, I’m going to rename this Topic to make it a little more generalized.
Basically the problem is triage: usually projects that have both a Discourse instance and a public GitHub issue tracker tend to have their users concentrated more on the Discourse instance, and when a user Topic is more properly a GitHub Issue, sometimes there will be friction in the process of the Topic finding its way to the people responsible for handling it.
Another way of looking at this is as inboxes or buckets: if end users are more active on the Discourse instance, and the developers are more active on the GitHub repository, essentially the developers or someone tasked with triage has to keep track of multiple redundant places for people to post their problems and figure out a consistent way of migrating Issues and Topics when necessary.
What I’m imagining with GitHub Issue sync is something like the Discourse WordPress plugin, where the Issue tracker and a corresponding Discourse Category are, to the end user, different views for the same underlying set of conversations.
Again, I’m not in a position to spend money on this feature. I’m posting here based on my experience and frustration with it being unclear where to post different types of feedback on certain projects and the tendency of misplaced feedback to fall through the cracks.
(Oh, and preferably there would be exactly the same functionality for Gitlab as for GitHub…)