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.
post
Branch on every commit. Never delete. If something needs to be rolled back, merge it back into HEAD. Conflict resolution only through melee combat.
I like prod because it makes less assumptions on stability. It is what is being used, good luck with the rest.
“live” didn’t make it onto the list, I see.
Looks like it died.
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.
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.
"Untitled"
Production made me lol
Uhh, Daddy, obviously.
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.
nowadays, mommy
Moab is “mouth over anus & balls”.
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)
Hey Linus did you merge my branch into mommy? I really want to get it out.
Our development branch is "working", then we have specific dated snapshots where we run our datasets through our programs.
top 50 comments