What about joe? Because the engineer who bootstrapped the project mistakenly put his name as the mainline branch and we realized it far too late during the lifecycle and the team decided to keep the branch name because it's hilarious.
this post was submitted on 16 Aug 2025
583 points (97.9% liked)
Programmer Humor
26691 readers
1519 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Joe who?
Joe mama
load more comments
(1 replies)
Branch on every commit. Never delete. If something needs to be rolled back, merge it back into HEAD. Conflict resolution only through melee combat.
Never merge. Only cherry pick.
You have met every team I have ever worked with apparently
How have you survived in this world without exploding into a million little fiery merge conflicts?
I let the interns handle those. If they survive, they get bragging rights.
Conflict resolution only through melee combat.
Wrestle with Jeff, Prepare for death.
HEAD
It's master3. Don't question it!
prod
I like prod because it makes less assumptions on stability. It is what is being used, good luck with the rest.
load more comments
(1 replies)
“live” didn’t make it onto the list, I see.
Looks like it died.
Live and let die?
load more comments
(1 replies)
Boring answer: older repos are master, newer ones are main. I've worked at companies that did other things such as having the prod branch be a branch called prod.
hunter2
Why would you name a branch just 7 asterisks?
🤡 for master
👽 for test
💩 for dev
Chaotic Evil should be the current sha hash.
belay your panic. even mommy cannot save you.
"testing"
don't wake up. fourth row just dropped.
Develop should be Chaotic Evil.
This is what is used where I work. I have never and will never understand why.
load more comments
(1 replies)
Feel like lawful evil fits better for master
"test"
It's goshujin-sama
Yall have multiple branches?
"fuck it, it''s friday"
release
we use git-flow in our company. So release is already another branch.
"Untitled"
Untitled-project2_final_fixed-3.zip
(empty string)
Production made me lol
it's a one way ticket to having "who's on first?" problems
If you never pu5 anything into production then you never fail
qa.
All development happens in feature branches. Someone other than the original developer needs to build and test the feature on our development servers. If successful it gets merged into qa, where it gets built and tested against it qa servers. Production build are tags on qa.
Latest
Some of my repos on github use either main or master.
branch (i always commit directly to the main branch so i only have one, so why bother naming it. also YOU CANT STOP ME FROM DOING IT BWAHAHAHAHAHA)
Develop
develop
Khorne
Our development branch is "working", then we have specific dated snapshots where we run our datasets through our programs.
Hey Linus did you merge my branch into mommy? I really want to get it out.
Main is QA. Production is release branches.
view more: next ›