Göran W

I agree that text, binary, LFS should all use consistent icons, since they are all regular files (except LFS, but these should ideally be treated rather transparently as diffs of...

Actually, git-status also treats submodules a bit special: > Submodules have more state and instead report > M = the submodule has a different HEAD than recorded in the index...

OK, sorry, I just realized that we (of course) need to distinguish between Modified/Added/Deleted/(Renamed?) for submodule Change. But could there then instead be ANY (other) indication in the list that...

A grayscale submodule (box/package) icon to the right of the submodule name/path would do fine.

I.e. something like this would be fine, just some (any) indication that a change-list item is actually a submodule...  Could also be placed to the left of the name/path,...

The main motivation for indicating submodules (with a special icon/color or similar) in CHANGES lists/trees (and ideally even in FILES lists/trees) is that they are neither (normal) files nor directories....

One of my use-cases is to provide a Custom "Rename remote branch" Action (see #1457). Separating a remote branch name (like `origin/my-branch`) into a Remote part (`${REMOTE}` = `origin`) and...

Thank you, this is great! However, something is still missing... Since there is already a built-in '`Rename `' context-command for Local Branches, I want my Custom Action "Rename Remote Branch"...

Related commit 4e01270cc08702e6743d968f14f2df7b1178ffeb changes the `${BRANCH}` variable to contain only the pure branch name, just as I requested - thank you! It also adds a new variable `${BRANCH_FRIENDLY_NAME}` (which IMHO...

WinGet is no longer an option (instead [Scoop](https://scoop.sh/) is recommended), see https://github.com/sourcegit-scm/sourcegit/issues/1931#issuecomment-3596476885.