https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

Perhaps with separate fields for:

• Log output - Enable "C_Cpp.loggingLevel": "Debug" and provide the contents of the C/C++ output channel leading up to the issue.
• Log Diagnostics output - Run C/C++: Log Diagnostics with the source file open that is reproducing the issue.
• 'c_cpp_properties.json` contents
• Any explicitly set C_cpp settings
• Call Stacks - If the issue is a crash or hang, how to attach a debugger to cpptools or cpptools-srv to get call stacks.