You must log in or # to comment.
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
Yall have multiple branches?
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.
It’s master3. Don’t question it!
Developshould be Chaotic Evil.“test”
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.
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)
“Untitled”
Untitled-project2_final_fixed-3.zip
(empty string)
HEAD
Moab is “mouth over anus & balls”.
Even better
Some of my repos on github use either main or master.
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?
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.
