# Bidirectional sync between Discourse Topics/Categories and GitHub/Gitlab Issue Trackers **URL:** https://meta.discourse.org/t/bidirectional-sync-between-discourse-topics-categories-and-github-gitlab-issue-trackers/203780 **Category:** Feature **Tags:** code-review **Created:** [September 16, 2021, 5:10pm UTC](https://meta.discourse.org/t/bidirectional-sync-between-discourse-topics-categories-and-github-gitlab-issue-trackers/203780 "2021-09-16T17:10:52Z") **Posts on this page:** 1 **Showing post:** 1
### Author: ![elsiehupp](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elsiehupp/32/578380_2.png) [@elsiehupp](https://meta.discourse.org/u/elsiehupp) #### Post date: [September 16, 2021, 5:10pm UTC](https://meta.discourse.org/t/bidirectional-sync-between-discourse-topics-categories-and-github-gitlab-issue-trackers/203780/1 "2021-09-16T17:10:52Z")
I’m replying here rather than starting a new Topic. Other related Topics are [here](https://meta.discourse.org/t/migrate-a-topic-to-github/45058), [here](https://meta.discourse.org/t/mention-github-issues/131970), [here](https://meta.discourse.org/t/code-review-issues-migrator/167409) and [here](https://meta.discourse.org/t/add-issues-support-to-github-plugin/196315). (This Topic thread in particular is just both relatively recent and relatively long.) I asked on [the Topic for Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142) about whether it had any support for GitHub Issues: > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/52): > > I found my way here from the link at the top of [Introducing GitHub Issues to Discourse](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671). The plugin discussed in that topic specifically synchronizes GitHub Issues. > > It is unclear to me whether Discourse Code Review synchronizes Issue creation in addition to [“Issue comments”](https://docs.github.com/en/developers/webhooks-and-events/events/github-event-types#issuecommentevent), commits, Pull Requests, and the like. Looking at the GitHub REST API doesn’t really make it any clearer to me, mainly due to my unfamiliarity, though [`IssuesEvent`](https://docs.github.com/en/developers/webhooks-and-events/events/github-event-types#issuesevent) does appear to be a separate type from `IssueCommentEvent` . > > Could you update the above documentation to specify whether or not Discourse Code Review synchronizes Issue creation and other Issue events in addition to Issue Comments? Also, if this is indeed supported, and if you are so inclined, could you add instructions for setting up Issue syncing without necessarily setting up Pull Review syncing? Thanks! > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/54): > > Hi @osioke—thanks for replying! > > In the following quote: > > > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/1): > > > > Each commit to a repository becomes a topic. Replies to the topic are mirrored on GitHub. > > Issues (and Pull Requests) aren’t the same thing as commits. An Issue doesn’t even involve a commit. It makes sense that comments on commits would synchronize with Discourse, but that doesn’t say anything about new Issues. > > (I don’t know how one would create a Pull Request from Discourse, considering everything involved, but an Issue is just a glorified comment thread that’s not directly tied to any code, so creating a new Topic and having it appear as an Issue would make as much sense as the reverse.) > > > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/53): > > > > What about these images, do they not help? > > I hadn’t looked closely at the images previously—instead I had done “search within page” in my browser—but on closer inspection the images only show comments on commits, not creating or syncing Issues or Pull Requests. > > Specifically the use case I’m asking about is when a project has both a Discourse and a GitHub Issue Tracker, and [sometimes people post in one when they should post in the other](https://github.com/nextcloud/nextcloud-snap/issues/1817#issuecomment-903365844). Having Issue threads bidirectionally synchronize between Discourse and GitHub would help avoid the problem of misplaced threads falling through the cracks. > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/55): > > Hi Elsie! I recently tested the code review plugin for Discourse for Teams. This plugin only syncs commits and pull requests from github → discourse, and replies to commits and pull requests from Discourse → github. It does not touch github issues at all. > > I can see how it would be useful to select and move issues to discourse. I am not sure of the status of the tool described in [Introducing GitHub Issues to Discourse](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671) - as indicated it is not maintained and I am not able to find it myself. > [@Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142/56): > > It’s unfortunate that Discourse Code Review doesn’t support Issues at this time. > > The tool described in [Introducing GitHub Issues to Discourse](https://meta.discourse.org/t/introducing-github-issues-to-discourse/46671) is a one-way import rather than a two-way sync, so it isn’t really suitable for all cases even if it indeed still works despite being unmaintained. > > I imagine the older tool’s codebase could be a useful starting point for adding Issue support to Discourse Code Review, though. tl;dr some degree of bidirectional sync of GitHub Issues and Discourse Topics as a feature of Discourse Code Review could be helpful for projects that currently have some ambiguity and redundancy between the two. Cross-posting here because the other thread auto-deletes replies after a month. --- _[View the full topic](https://meta.discourse.org/t/bidirectional-sync-between-discourse-topics-categories-and-github-gitlab-issue-trackers/203780)._