Post #2617038
2025-09-26 12:35 UTC
@agowa338@chaos.social 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
Replies (2)
-
@agowa338@chaos.social 2025-09-26 12:38
@mia@tearoom.tearmoon.com 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@chaos.social 2025-09-26 12:39
@mia@tearoom.tearmoon.com Also this sounds like you should look into git worktrees.