Using remote HEAD for base branch

[toy]

Following discussion #4348 I'm wondering why not use remote HEAD (like refs/remotes/origin/HEAD) for determining the base branch instead of requiring by default to add git.mainBranches config?

[stefanhaller]

instead of requiring by default to add git.mainBranches config

Lazygit does not require you to set this config. In the vast majority of cases the default works fine and you can leave this unset.

The main reason people need (or want) to set the config is that they have additional main branches besides main, e.g. develop, and using the remote HEAD doesn't help with that.

The only scenario that I can imagine where your suggestion would help is if a repo uses a different name for its main branch than main or master (e.g. trunk). This should be really rare though.

[toy]

Sorry, I meant requiring in case the main branch is different from main/master.

I'm working on a project where this is the case (dev is used) and for me to use the feature required to ask my colleague and change configuration, so I feel not lazy enough ;)
Automatic usage of remote HEAD would really reduce the friction in my and similar cases, but I understand if is not really requested feature and/or it is not simple to implement

[stefanhaller]

I see, thanks for clarifying. Well, it's not totally trivial to implement, and my guess would be that only few people are affected by it (I don't have numbers on that though), so improving this is not high on my priority list.

[toy]

I also found that mainBranches doesn't support globbing (#5246), so in the end created a script that runs before opening lazygit and creates the .git/lazygit.yml with needed config.

One a bit unexpected thing about the config is that I expected it to be at git dir (git rev-parse --git-dir) also for additional worktrees, but it was at common dir (git rev-parse --git-common-dir), but I can understand the reason for that too