Use full refname instead of short to prevent disambiguation with tag

In the unlikely scenario that you have a remote branch on `origin` called
`foo`, and a local tag called `origin/foo`, git changes the behavior of
the previous command such that it produces

```
$ git for-each-ref --sort=refname --format=%(refname:short) refs/remotes

origin/branch1
remotes/origin/foo
```

with `remotes/` prepended. Presumably this is to disambiguate it from
the local tag `origin/foo`. Unfortunately, this breaks the existing
behavior of this function, so the remote branch is never shown.

By changing the command, we now get
```
$ git for-each-ref --sort=refname --format=%(refname) refs/remotes

refs/remotes/origin/branch1
refs/remotes/origin/foo
```

This allows easy parsing based on the `/`, and none of the code outside
this function has to change.

----

We previously were not showing remote HEADs for modern git versions
based on how they were formatted from "%(refname:short)", so we continue
that practice as a default, but we allow users the ability to show them
if they want

Author: Chris McDonnell

docs/Config.md

@@ -347,6 +347,9 @@ git:
   # If true, pass the --all arg to git fetch
   fetchAll: true
 
+  # If true, show remote HEADs in the remote branches tab
+  showRemoteHeads: false
+
   # If true, lazygit will automatically stage files that used to have merge
   # conflicts but no longer do; and it will also ask you if you want to
   # continue a merge or rebase if you've resolved all conflicts. If false, it

pkg/commands/git_commands/remote_loader.go

@@ -96,19 +96,23 @@ func (self *RemoteLoader) getRemoteBranchesByRemoteName() (map[string][]*models.
 
 	cmdArgs := NewGitCmd("for-each-ref").
 		Arg(fmt.Sprintf("--sort=%s", sortOrder)).
-		Arg("--format=%(refname:short)").
+		Arg("--format=%(refname)").
 		Arg("refs/remotes").
 		ToArgv()
 
 	err := self.cmd.New(cmdArgs).DontLog().RunAndProcessLines(func(line string) (bool, error) {
 		line = strings.TrimSpace(line)
 
-		split := strings.SplitN(line, "/", 2)
-		if len(split) != 2 {
+		split := strings.SplitN(line, "/", 4)
+		if len(split) != 4 {
+			return false, nil
+		}
+		remoteName := split[2]
+		name := split[3]
+
+		if !self.UserConfig().Git.ShowRemoteHeads && name == "HEAD" {
 			return false, nil
 		}
-		remoteName := split[0]
-		name := split[1]
 
 		_, ok := remoteBranchesByRemoteName[remoteName]
 		if !ok {

pkg/config/user_config.go

@@ -251,6 +251,8 @@ type GitConfig struct {
 	AutoForwardBranches string `yaml:"autoForwardBranches" jsonschema:"enum=none,enum=onlyMainBranches,enum=allBranches"`
 	// If true, pass the --all arg to git fetch
 	FetchAll bool `yaml:"fetchAll"`
+	// If true, show remote HEADs in the remote branches tab
+	ShowRemoteHeads bool `yaml:"showRemoteHeads"`
 	// If true, lazygit will automatically stage files that used to have merge
 	// conflicts but no longer do; and it will also ask you if you want to
 	// continue a merge or rebase if you've resolved all conflicts. If false, it
@@ -822,6 +824,7 @@ func GetDefaultConfig() *UserConfig {
 			AutoRefresh:                  true,
 			AutoForwardBranches:          "onlyMainBranches",
 			FetchAll:                     true,
+			ShowRemoteHeads:              false,
 			AutoStageResolvedConflicts:   true,
 			BranchLogCmd:                 "git log --graph --color=always --abbrev-commit --decorate --date=relative --pretty=medium {{branchName}} --",
 			AllBranchesLogCmds:           []string{"git log --graph --all --color=always --abbrev-commit --decorate --date=relative  --pretty=medium"},

schema/config.json

@@ -339,6 +339,11 @@
           "description": "If true, pass the --all arg to git fetch",
           "default": true
         },
+        "showRemoteHeads": {
+          "type": "boolean",
+          "description": "If true, show remote HEADs in the remote branches tab",
+          "default": false
+        },
         "autoStageResolvedConflicts": {
           "type": "boolean",
           "description": "If true, lazygit will automatically stage files that used to have merge\nconflicts but no longer do; and it will also ask you if you want to\ncontinue a merge or rebase if you've resolved all conflicts. If false, it\nwon't do either of these things.",