Hi @vsch

# isn't used in GitQ to trigger showing issues. Instead, only the GitHub url is supported.

Would it be possible to add completions for issues when using #?

GitHub does have the API to get issues.

Is GitQ source code available? I could take a look if I can start being useful and add a feature.

It is half of the GitHub integration which I think would be great to have in GitQ. The other is being able to refer to GitQ conversations from GitHub and starting a GitQ conversation from a GitHub Issue. I have a few ideas on how it can be done without needing GitHub to provide an API for it.

Hi @vsch

I don't want to add auto completions for GitHub issues, instead, maybe for GitQ topics in future version.

The source code is not available as I'm thinking to refactor the whole architecture, especially for the frontend. Currently, the frontend of GitQ is using wicket, and I'm going to use React instead. So, maybe after all the refactoring finished, we'll open source it.

I have added you to the collaborator to the repository, so you can access the source code now, the current site is running on 1.0.x branch.

@steveluo, accepted.

I will do PRs so you can review. Don't worry about the refactoring before release.

You would be surprised how much input users provide and help you get the project moving faster. I would not have half the features in flexmark-java or Markdown Navigator if it was not for user suggestions.

BTW, what IDE do you use? If it is intelliJ or any of the JetBrains IDEs I will send you a Markdown Navigator license so you can enjoy working with Markdown in comfort.

@vsch I'm using IntelliJ and have added a very simple guide for how to run GitQ in README. Let me know if you have any problems.