Enable Github Discussions

[i-ky]

People ask configuration-related questions by opening Issues. People get answers. People close issues. Closed issues are excluded from issue search by default. This makes it harder for other people to find answers to the same questions leading to more issues.

Github Discussions provide a platform dedicated to questions and answers. Useful comments can get upvoted and accepted as a solution, answered questions are not excluded from search.

Consider enabling Discussions for this repository and steering people into creating a discussion before they create issues. By the way, issue (even an old one) can be converted into discussion too.

[HighCommander4]

We have them enabled in the main clangd repo: https://github.com/clangd/clangd/discussions.

@sam-mccall I recall you enabled them as sort of a trial. Do you think we should enable them in vscode-clangd too?

[kadircet]

I am not sure if we really have FAQ-like discussions in vscode-clangd repo (can't say that I've been following thoroughly, so happy to be proven wrong). I think most of those discussions actually happen (or belong to) clangd/clangd repo (especially the config related ones, I believe they are not about the vscode's workspace settings but rather clangd configs, as we have relatively few knobs specific to vscode)

[i-ky]

I am not sure if we really have FAQ-like discussions in vscode-clangd repo (can't say that I've been following thoroughly, so happy to be proven wrong).

Few examples of closed issues that did not result in any changes to clangd or extension, but contain somewhat valuable information and configuration hints:

• #4
• #100
• #163
• #189
• #191
• #218
• #219
• #230
• #264
• #339
• #345
• #349
• #399
• #452
• #477
• #488
• #555

I think most of those discussions actually happen (or belong to) clangd/clangd repo (especially the config related ones, I believe they are not about the vscode's workspace settings but rather clangd configs, as we have relatively few knobs specific to vscode)

Even so, I doubt that every user will be qualified enough to correctly classify which component their issue belongs to: clangd, extension or VS Code itself. And with cross-reference support by Github there is no harm in having some duplication of topics among repositories.