What do you call your production branch?
-
This post did not contain any content.
-
This post did not contain any content.
“live” didn’t make it onto the list, I see.
-
This post did not contain any content.wrote last edited by [email protected]
Branch on every commit. Never delete. If something needs to be rolled back, merge it back into HEAD. Conflict resolution only through melee combat.
-
This post did not contain any content.
Some of my repos on github use either main or master.
-
“live” didn’t make it onto the list, I see.
wrote last edited by [email protected]Looks like it died.
-
This post did not contain any content.
"fuck it, it''s friday"
-
Branch on every commit. Never delete. If something needs to be rolled back, merge it back into HEAD. Conflict resolution only through melee combat.
How have you survived in this world without exploding into a million little fiery merge conflicts?
-
This post did not contain any content.wrote last edited by [email protected]
for master
for test
for dev -
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.
-
Branch on every commit. Never delete. If something needs to be rolled back, merge it back into HEAD. Conflict resolution only through melee combat.
You have met every team I have ever worked with apparently
-
This post did not contain any content.
Production made me lol
-
Looks like it died.
Live and let die?
-
This post did not contain any content.
Uhh, Daddy, obviously.
-
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.
-
This post did not contain any content.
nowadays, mommy
-
This post did not contain any content.
Our development branch is "working", then we have specific dated snapshots where we run our datasets through our programs.
-
Production made me lol
If you never pu5 anything into production then you never fail
-
Production made me lol
it's a one way ticket to having "who's on first?" problems
-
This post did not contain any content.
It's master3. Don't question it!
-
This post did not contain any content.
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.
