-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authorship turned on by default for docker compose files #2153
Comments
Same problem here. |
This comment was marked as resolved.
This comment was marked as resolved.
GitLens didn't change anything here. My guess is that another extension (Docker?) is now providing language services (symbols, etc) for docker compose files and GitLens is now able to consume them to provide Git CodeLens. These can be customized per-language, e.g. "[dockerfile][dockercompose]": {
"gitlens.codeLens.scopes": [
"document"
]
} That should limit the Git CodeLens to only the document root. I've also added the above to the GitLens default configuration, so in tomorrow's pre-release this should just work out of the box. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
GitLens Version
v12.1.2
VS Code Version
Version: 1.70.2 (Universal)
Commit: e4503b30fc78200f846c62cf8091b76ff5547662
Date: 2022-08-16T05:36:37.829Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Darwin x64 21.6.0
Git Version
git version 2.37.2
Description
Gitlens has authorship turned on for docker compose files by default. Unless my fat fingers toggled it somehow but in two years it has yet to happen. So I had to go into settings and turn it off. Strange behaviour... i figured it came in a update.
Logs, Screenshots, Screen Captures, etc
The text was updated successfully, but these errors were encountered: