@agowa338 it might be because I am not a programmer — since childhood I only ever dealt with hobby-tier stuff (Z80/8080/M680x0/PowerPC Assembler, Ada, C#, Rust) and as a linguistics major only had 2 years of mandatory C in the university
so git is inscrutable to me; I do not understand why is it git stash list but git branch --list, etc.
@agowa338 a project that I collaborate on has dozens of branches and it is easy to get lost sometimes haha
git stash list is used by me a lot for weird reasons: I have a git checkout of the FreeBSD ports tree that I want to keep as close to the original as possible, so all my temporary patches are stashed when I'm updating the tree
@mia But how often do you really need to know about all of them?
Like even for big projects it's at most 2-3 branches.
1 The main/master branch of the upstream project
2 Your patch-* branch
3 When someone sent you a diff/patch for your patch or you want to merge in some of their changes into yours.
And even for bigger projects like ansible where backporting is a thing that is basically because of the process not really different either just switch "main/master" with whatever version that pr is
@agowa338 it's a mobile game and they have separate branches for separate features/events/etc… and loc strings are spread all over those
it's terrible but that's what they have