Post B530IhYUOEkBAyMnB2 by cccpresser@chaos.social
 (DIR) More posts by cccpresser@chaos.social
 (DIR) Post #B52isGjJnxu3EFF4Qi by lethalbit@chaos.social
       0 likes, 0 repeats
       
       ```# git branch | wc -l41```ough,
       
 (DIR) Post #B52z5N4D9bgxuiHfcm by cccpresser@chaos.social
       0 likes, 0 repeats
       
       @lethalbit /me laughs in maintainer.Got 278, 112 and 118 in the 3 repos I do most stuff.
       
 (DIR) Post #B52zV65QuPOGmO7fTE by lethalbit@chaos.social
       0 likes, 0 repeats
       
       @cccpresser Yeah, I know how it be, it's just a little overwhelming, ya know?
       
 (DIR) Post #B530IhYUOEkBAyMnB2 by cccpresser@chaos.social
       0 likes, 0 repeats
       
       @lethalbit Indeed, it is really overwhelming.Pure numbers don't really tell how much work and mental load sits in each branch. Fortunately most of mine already merged or stale.In reality its similar to your 41 in the sense of 'open issues'.
       
 (DIR) Post #B5312ynwacodzif95E by lethalbit@chaos.social
       0 likes, 0 repeats
       
       @cccpresser Yeah, that's why I tend to prune early and often, all 41 are active and in-progress, anything that's gotten merged has been clipped.And as I operate on a rebase/ff-only merge flow, it's not too bad, no merge commits in sight to make the history a messy tangle