git log --graph --all would show something like:

X:\Vite\Repository\LocalControl>git log --graph --all
* commit c2234c6162cae9e7bfe5013a76b6c381092046fb (origin/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler, Repository/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler)
| Author: Skybuck Flying [off-list ref]
| Date:   Thu Dec 11 10:15:51 2025 +0100
|
|     SystemPrompt.md +FPC testing, +common/types uses.
|
|     SystemPrompt.md updated for:
|     + Use FPCUnit for testing with Free Pascal Compiler.
|     + Special directives for common/types imports/uses clausules.

origin is a remote (the github remote)
Repository is also a remote (locally on my disk).

Both branches are in red:
origin/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler
Repository/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler

There is the possibility when creating branches in all kinds of ways of accidently naming it the same as the remote, so it's not really a remote, but it's just some kind of branch name with happens to have the same remote name.

Maybe these remote branch names are just one string and the difference don't matter or maybe it does matter, I think it does matter, if it does matter/stored differently then the idea is to:

Allow mixed colors in these remote branches.

So the origin part becomes pink.
So the Repository part becomes pink.

So that it's more clear what part of it is a *true* remote and what part of it is a *true* branch.

Further info:

X:\Vite\Repository\LocalControl>git remote -v
Repository      X:\Vite\Repository\Mirror (fetch)
Repository      X:\Vite\Repository\Mirror (push)
origin  https://github.com/SkybuckFlying/SkyVite.git (fetch)
origin  https://github.com/SkybuckFlying/SkyVite.git (push)
upstream        https://github.com/vitelabs/go-vite.git (fetch)
upstream        https://github.com/vitelabs/go-vite.git (push)

Bye,
  For now,
   Skybuck.

P.S.:

Here is the AI version of it, in case you find it easier to read :):

Hello,

When running `git log --graph --all`, I see decorations like:

* commit c2234c6162cae9e7bfe5013a76b6c381092046fb
  (origin/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler,
   Repository/Branch/Feature/Delphi/SystemPromptUpdateForTestingUsingFreePascalCompiler)

Both `origin/...` and `Repository/...` are shown in red. In my setup:

- origin = GitHub remote
- Repository = local mirror remote (X:\Vite\Repository\Mirror)

This makes it hard to visually distinguish the *remote name* from the *branch name*.
It’s also possible to accidentally create a branch whose name collides with a remote
name, which adds to the confusion.

**Proposal:**
Allow mixed colors for remote branch decorations, so that:
- The remote part (`origin`, `Repository`, etc.) is shown in one color (e.g. pink).
- The branch part (`Branch/Feature/...`) remains in another color (e.g. red).

This would make it clearer which part of the decoration is the true remote and which
part is the branch name.

Current remotes in my repo:
  Repository      X:\Vite\Repository\Mirror (fetch/push)
  origin          https://github.com/SkybuckFlying/SkyVite.git (fetch/push)
  upstream        https://github.com/vitelabs/go-vite.git (fetch/push)

Thanks for considering,
  Skybuck Flying