Hi. In COMMITS pane, the default ${❰ tips ❱➤ } shows branches but does not show tags.
The circled commit below appears in both COMMITS and TAGS pane. However, the COMMITS pane only shows master and does not show master, v1.3.20201027
I am expecting ${tips} to do as its documentation writes. To show branches and tags at a commit.
Also expecting it to show the same information as in a git log. Here is that log for this same commit
Setup
GitLens Version: 11.0.6
Git Version: git version 2.29.2
Version: 1.51.1 (system setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19042
Steps to Reproduce:
Setup OS, vscode, git, and extensions as above
Setup gpg signing. Set commit.gpgSign, tag.gpgSign, and tag.forceSignAnnotated all true in git global user settings.
Make commits on master branch
Tag last commit
Make new branch foobar, checkout foobar
Make several commits
Switch to source control section in vscode
open COMMITS pane and view the entry for the commit that was tagged in step 4
Result
The commit in the COMMITS pane shows only master
Expected
The commit in the COMMITS pane to show master and the tag made in step 4
The text was updated successfully, but these errors were encountered:
Hi. In COMMITS pane, the default
${❰ tips ❱➤ }
shows branches but does not show tags.The circled commit below appears in both COMMITS and TAGS pane. However, the COMMITS pane only shows
master
and does not showmaster, v1.3.20201027
I am expecting ${tips} to do as its documentation writes. To show branches and tags at a commit.
Also expecting it to show the same information as in a
git log
. Here is that log for this same commitSetup
Steps to Reproduce:
commit.gpgSign
,tag.gpgSign
, andtag.forceSignAnnotated
alltrue
in git global user settings.Result
The commit in the COMMITS pane shows only
master
Expected
The commit in the COMMITS pane to show
master
and the tag made in step 4The text was updated successfully, but these errors were encountered: