Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
gitlens.defaultDateStyle
not working in Commit Details viewgitlens.experimental.openChangesInMultiDiffEditor
setting to gitlens.views.openChangesInMultiDiffEditor
, which is enabled by default, to specify whether to open changes in the multi-diff editor (single tab) or in individual diff editors (multiple tabs)1.86
or later, or VS Code 1.85
with multiDiffEditor.experimental.enabled
enabled1.86
or later, or VS Code 1.85
with multiDiffEditor.experimental.enabled
enabledgitlens.experimental.allowAnnotationsWhenDirty
setting to gitlens.fileAnnotations.preserveWhileEditing
, which is enabled by default, to specify whether file annotations will be preserved while editing — closes #1988, #3016
gitlens.advanced.blame.delayAfterEdit
setting to control how long to wait (defaults to 5s) before the annotation will update while the file is still dirty, which only applies if the file is under the gitlens.advanced.sizeThresholdAfterEdit
setting threshold (defaults to 5000 lines)gitlens.blame.fontFamily
, gitlens.blame.fontSize
, gitlens.blame.fontWeight
settings to specify the font (family, size, and weight respectively) of the File Blame annotations — closes #3134
gitlens.experimental.openChangesInMultiDiffEditor
setting to gitlens.views.openChangesInMultiDiffEditor
as it is no longer experimental and enabled by defaulthttps://gitkraken.dev/link/r/{repoId}/f/{filePath}?[url={remoteUrl}|path={repoPath}]&lines={lines}&ref={ref}
gitlens.experimental.allowAnnotationsWhenDirty
setting to specify whether file annotations are allowed on files with unsaved changes (dirty) — closes #1988, #3016
gitlens.advanced.blame.delayAfterEdit
setting to control how long to wait (defaults to 5s) before the annotation will update while the file is still dirty, which only applies if the file is under the gitlens.advanced.sizeThresholdAfterEdit
setting threshold (defaults to 5000 lines)gitlens.fileAnnotations.dismissOnEscape
setting to specify whether pressing the ESC
key dismisses the active file annotations — closes #3016
file:readme.txt
, we will treat it as file:**/readme.txt
, or if you enter file:readme
it will be treated as file:*readme*
gitlens.experimental.nativeGit
setting as it is now the default experience — closes #3055
1.85
or later and multiDiffEditor.experimental.enabled
to be enabledgitlens.experimental.openChangesInMultiDiffEditor
setting to specify whether to open multiple changes in VS Code's experimental multi-diff editor (single tab) or in individual diff editors (multiple tabs)
1.85
or later and multiDiffEditor.experimental.enabled
to be enabledgitlens.views.openOnlyChangedFiles
) command in the views)
gitlens.cloudPatches.enabled
setting to specificy whether to enable Cloud Patches (defaults to true
)gitlens.graph.allowMultiple
setting to specify whether to allow opening multiple instances of the Commit Graph in the editor areagitlens.focus.allowMultiple
setting to specify whether to allow opening multiple instances of the Focus in the editor areagitlens.visualHistory.allowMultiple
setting to specify whether to allow opening multiple instances of the Visual File History in the editor area1.84.0-insider
only)
gitlens.ai.experimental.generateCommitMessage.enabled
setting to specify whether to enable GitLens' experimental, AI-powered, on-demand commit message generation — closes #2652
gitlens.sortRepositoriesBy
setting to specify how repositories are sorted in quick pick menus and views by Aidos Kanapyanov (@aidoskanapyanov)gitlens.liveshare.enabled
setting to specify whether to enable integration with Visual Studio Live Sharegit.useForcePushWithLease
and git.useForcePushIfIncludes
settings when force pushingline
to the gitlens.heatmap.locations
setting