Git makes it easy to search through historical changes they said. Git is amazing when working in teams they said.

It sure is.

If your coworkers do not commit every time they burp or fart, do not use "🚀" or "✨" or "fix" as a commit message, and do not push all their shitty experimental broken branches without cleaning up.

I'm surprised there are no piles of fecal matter behind their desk chairs.

Duuuude, thats a big tree o branches 🤷‍♂️👏

git gud

@snaz All my coworkers use that atlassian tool for git, and while I'm sure it can rebase and cherrypick and clean up merged branches... They're all too lazy to learn anything beyond three button clicks.

Holy shitballs....

@bittersweet maybe you could inform the team that they can use more than one repository

@dev-n-u-l-l Maybe I could inform the team that they are all fired 😄

Just for the record, how many people commit on this repository on a regular basis?

'cause man, 2k branches, are you growing a forest or what?

@Commodore About 15 devs commit regularly to this part of the project.

I cringed. Then my cringe cringed. Then I aftercringed.

@bittersweet fif-fucking-teen Jesus Christ. What in the hell are they each doing with over 150 branches a piece! I mean whatttttt! We all gonna sit down and read Git For Humans, fucking 5th grade popcorn reading style cause I do need to verify that y’all motherfuckers can read

@jeeper

git checkout master
git checkout -b package-update
edit file
commit ...
git push origin HEAD
git checkout master
git checkout -b moving-a-test
edit file
commit ...
git push origin HEAD
git checkout master
git checkout -b fixing-typo

etc.

It's not the worst thing to make a lot of branches, but they merge PRs on github without cleaning up merged branches.

It's like cooking, using cups and spoons to measure everything, and regularly swiping everything on the floor instead of washing dishes.

Should rename branches to botanic garden methinks 🤷‍♂️

@karma

First thing I did was make a git alias called "git deforestation" linked to

git checkout master && git branch -r --merged | grep -v master | sed "s/origin\///" | xargs -n 1 git push --delete origin

Which deletes all remote branches which are completely merged.

@bittersweet lol got the exact same thing but call it "git spring" for spring cleaning.
I'll add deforestation as a second alias though 😁

Hahaha. Commit message: code rearranged

@MySlugLikesSalt I like a ton of commits, but only when their commit messages say something useful.

I try to think in terms of "if I have to revert these changes, what would be nice states to end up in". So that could be after adding a small method, but not halfway a sentence.