"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...
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...
GITLens switch to commit made my newer commits disappear This is scary, to those new to Git. But don't worry: all the commits are still there. Various GUIs, including Visual Studio, block access to Git (which could be good or bad, depending on your point ... torek 480k answered ...
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...
Improves the Switch command to no longer fail when trying to switch to a branch that is linked to another worktree and instead offers to open the worktree Changes branch/tag “tips” that are show on commits in many GitLens views to be truncated to 11 characters by default to avoid stealin...
and it's critical to Git being adistributedversion control system. But it also means that no Git commit can ever contain the raw hash ID of its futurechildrencommits, because we have no idea what those will be when we create the commit. Commitscanstore the "names" (hash IDs) of their...
(e=false) completed • No valid session was found [1ms] [2023-12-04 08:23:53.211] [ ca] SubscriptionService.ensureSession(e=false) completed [2ms] [2023-12-04 08:23:53.211] [ cf] GitProviderService.visibility [2023-12-04 08:23:53.211] [ d0] GitProviderService.visibilityCore [2023...
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...
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 ...
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...