"No commits could be found.":"No commits could be found.", "No remotes could be found.":"No remotes could be found.", "No stashes could be found.":"No stashes could be found.", "No file history could be found.":"No file history could be found.", "The line has uncomm...
GitLens isn’t just for solo developers—it’s designed to enhance team collaboration. Sharing code can be tricky without adding noise to your repository with extra commits or branches. GitLens simplifies this with Cloud Patches and Code Suggest, letting you share or propose changes to any file...
GitLens Source Control Views (Commits, Branches, Remotes, etc.) can now be grouped under a unified “GitLens” view. You can navigate grouped views by clicking the icons in the new “GitLens” view, or detach them to be displayed as individual views in Source Control. This should reduce...
gitlens.advanced.fileHistoryFollowsRenames Specifies whether file histories will follow renames -- will affect how merge commits are shown in histories gitlens.advanced.maxListItems Specifies the maximum number of items to show in a list. Use 0 to specify no maximum gitlens.advanced.messages Spec...
gitlens.advanced.fileHistoryFollowsRenames Specifies whether file histories will follow renames -- will affect how merge commits are shown in histories gitlens.advanced.maxListItems Specifies the maximum number of items to show in a list. Use 0 to specify no maximum gitlens.advanced.messages Spec...
for each commit, and click on each to quickly browse through different commits. Maybe I just haven't found the right view. but it seems to have gone from intuitive to super user. and I think I would actually like to just rollback to previous version. I really don't need anything more...
If you are ahead of the upstream, an entry will be shown with the number of commits ahead. Choosing it will show a limited branch history quick pick menu containing just the commits ahead of the upstream If you are behind the upstream, an entry will be shown with the number of commits ...
right-click on files in past commits to open at revision causes nothing to occur click on doc icon on file in past commits to open at revision causes nothing to occur right click on files to compare with revision often (not always) causes actual command not found errors Looking at the gi...
Issue Type: Bug About every other time I start an interactive rebase (from a terminal) the editor comes up empty (No commits to rebase). However, the editor tab has an unsaved-indicator and if I inspect the contents of .git/rebase-merge/...
left arrow— goes back to previous step, if there is no text in the quick pick menu alt+left arrow, ctrl+left arrow, cmd+left arrow (macOS) — goes back to previous step Adds a new search command to search for specific commits — see below for more details on the all-new commit se...