Martin Deyanov

> Same issue. I manually committed and it woke up. My solution is to run a script (using AutoLaunch extension) that manually toggles "gitdoc.enabled": true, to false and a second...

I still have the same issue in a custom devcontainer. I have tried "gitdoc.enabled": true in both remote (devcontainer.json) and workspace (.vscode/settings.json) settings and gitdoc is not active on container...

> My current workaround is to not list `ms-vscode.cpptools` in the customizations/vscode/extensions, but instead to use a `postAttachCommand` to install it. That appears to allow gitdoc to get initialized successfully....