Skip Navigation

Programmer Humor @programming.dev

Hellfire103 @lemmy.ca

5d ago

What do you call your production branch?

52 comments

I’m using shenanigans now, fits the best methinks.
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.
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
- 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.
  
  Stick with the prod, its always a good idea to prod with the prod, stick with the prod.
hunter2
- Why would you name a branch just 7 asterisks?
Develop should be Chaotic Evil.
- This is what is used where I work. I have never and will never understand why.
  
  At some point in the past that was the only way to make the business run immediately when the boss said it needed to run immediately, and it's been that way ever since
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.
“live” didn’t make it onto the list, I see.
- Looks like it died.
  
  Live and let die?
- It's dead, Jim.
Yall have multiple branches?
Feel like lawful evil fits better for master
Chaotic Evil should be the current sha hash.
"Untitled"
- Untitled-project2_final_fixed-3.zip
- (empty string)
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)
It's goshujin-sama
belay your panic. even mommy cannot save you.
"testing"
don't wake up. fourth row just dropped.
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.
"test"
"fuck it, it''s friday"
release
- we use git-flow in our company. So release is already another branch.
Moab is “mouth over anus & balls”.
- Even better
Latest
Uhh, Daddy, obviously.
- I only push and pull daddy.
  Wait shit this is programming so i could probably push and pull mommy too.
  Both are great!
  
  I’d npm run watch you git push origin daddy
Develop
Khorne
nowadays, mommy
- Used to be daddy but we don't talk about that, she's much happier post-transition
Some of my repos on github use either main or master.
develop
Main is QA. Production is release branches.
Hey Linus did you merge my branch into mommy? I really want to get it out.
smirnoffcarkeysandabeer
Our development branch is "working", then we have specific dated snapshots where we run our datasets through our programs.
Evolution names like "mammal".

52 comments