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.
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.
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
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.
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.Joe who?
Joe mama
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.
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.
“live” didn’t make it onto the list, I see.
Looks like it died.
Live and let die?
It's dead, Jim.
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?
Chaotic Evil should be the current sha hash.
🤡 for master
👽 for test
💩 for dev
belay your panic. even mommy cannot save you.
"testing"
don't wake up. fourth row just dropped.
Developshould 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
"test"
It's
goshujin-samaYall 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)
Feel like lawful evil fits better for master
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.
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
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 watchyou git push origin daddyMoab is “mouth over anus & balls”.
Even better
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)
nowadays, mommy
Develop
Khorne
develop
Hey Linus did you merge my branch into mommy? I really want to get it out.
Main is QA. Production is release branches.
Our development branch is "working", then we have specific dated snapshots where we run our datasets through our programs.
smirnoffcarkeysandabeer
I’m using shenanigans now, fits the best methinks.
Evolution names like "mammal".