Re: Color remote repository part of a remote branch "pink" instead of red. I.E: [Feature Request] Mixed coloring for remote refs in git log --graph --all

>
> On Thu, Dec 11, 2025 at 4:46 AM Skybuck Flying <skybuck2000@hotmail.com> wrote:
> >
> > 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 <skybuck2000@hotmail.com>
> > | 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.
>
> "
> Perhaps try configuring color.decorate.branch or color.decorate.remoteBranch?
> "
>
> Hi,
>
> I haven't tried yet, the AI said it colors everything ? (in other words seperate/mixed colors not possible ?) hmmm..