# Discourse Code Review Questions
**URL:** https://meta.discourse.org/t/discourse-code-review-questions/401673
**Category:** Support
**Tags:** code-review
**Created:** [April 28, 2026, 7:08am UTC](https://meta.discourse.org/t/discourse-code-review-questions/401673 "2026-04-28T07:08:07Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@humblebumble](https://meta.discourse.org/u/humblebumble)
#### Post date: [April 28, 2026, 7:08am UTC](https://meta.discourse.org/t/discourse-code-review-questions/401673/1 "2026-04-28T07:08:07Z")
Hello,
we’re wanting to migrate to discourse and are playing around at the moment.
One goal we want to achieve is to get a bidirectional sync between a discourse thread and a GitHub issue.
For that I installed a discourse standard docker setup and also the Code Review Plugin ( [Discourse Code Review](https://meta.discourse.org/t/discourse-code-review/103142) )
What works:
- when I make a new issue which refers to a commit, this will be posted in discourse as a new thread in the selected category.
What don’t works:
When I make a new comment in an issue the webhook is made but the comment won’t show up in discourse.
Works as designed or a config issue? Which Log files can help?
The goal in the end is a category with a bidirectional sync between discourse and GitHub. For our community we want to use discourse. Our devs should only look at GitHub…
thanks in advance!
---
### Author:  [@humblebumble](https://meta.discourse.org/u/humblebumble)
#### Post date: [April 28, 2026, 9:43am UTC](https://meta.discourse.org/t/discourse-code-review-questions/401673/3 "2026-04-28T09:43:26Z")
Hey Lilly, thanks for your answer.
Yes, the GitHub plugin was the first place. This one pointed me to the code review plugin as the GitHub plugin won’t fulfill the requirements. There just a couple of threads with feature requests but without a solution.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [June 11, 2026, 6:39am UTC](https://meta.discourse.org/t/discourse-code-review-questions/401673/4 "2026-06-11T06:39:43Z")
Hey @humblebumble
Afaict, the plugin doesn’t support github _issue_ comments, despite `issue_comment` being listed as a subscribed webhook event in the plugin docs. The plugin is architecturally built only for commits and PRs. Regular GitHub Issues are not the same as PRs and will silently fail.
There is an open feature request for this you would want to add your vote to:
> [@Bidirectional sync between Discourse Topics/Categories and GitHub/Gitlab Issue Trackers](https://meta.discourse.org/t/bidirectional-sync-between-discourse-topics-categories-and-github-gitlab-issue-trackers/203780):
>
> 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: 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 ab…
But if you have the budget, asking in #Marketplace is probably the best direct route available.