@axEl7fB5@lemmy.cafe to linuxmemes@lemmy.worldEnglish • 1 month agoWhich git branch are you on?locklemmy.cafeimagemessage-square139fedilinkarrow-up1415arrow-down117
arrow-up1398arrow-down1imageWhich git branch are you on?locklemmy.cafe@axEl7fB5@lemmy.cafe to linuxmemes@lemmy.worldEnglish • 1 month agomessage-square139fedilink
minus-square@Lembot_0004@discuss.onlinelinkfedilink61•1 month agoMaster. I find this out of context fight against words pathetic.
minus-squareCubitOomlinkfedilinkEnglish46•edit-21 month agoMy scrum master said that we need new tickets to update the git branches and pipelines to use main instead of master since master was a bad word. I asked him what his job title was again and there was a pause. Then he said we can’t say that we are going to groom the code base anymore.
minus-square@childOfMagenta@jlai.lulinkfedilink13•1 month agoSwitch from your scrum main to your scrum alt.
minus-squaresnooggumslinkfedilinkEnglish8•1 month agoI’m gonna go ahead and assume your scrum main doesn’t groom themselves.
minus-square@BeigeAgenda@lemmy.calinkfedilink7•1 month agoIf we are not grooming the codebase, are we then waxing it? Or is it more eco-friendly to let the codebase grow wild and untrimmed?
minus-squarePhoturislinkfedilink6•1 month agoI agree that it’s pathetic. I’ve never been a fan of virtue signaling. In the other hand, “main” is easier to type than “master” (or “trunk,” for that matter). So I’ve made peace with it.
minus-squaresnooggumslinkfedilinkEnglish5•1 month agoTrunk would be better because of all the branches.
minus-squareDerpgonlinkfedilink19•edit-21 month agoWhy not change “walkie talkie” to “radio phone”? It is so much cleaner. Because change for the sake of change always brings more work than what it saves. Why change something that works and everyone recognizes it? Of course, if this debate was there when the standard was created…
minus-square@Lembot_0004@discuss.onlinelinkfedilink5•1 month agoBecause it is a historically settled down terminology that everyone understands and there is no adequate reason to change it.
minus-square@PotatoesFall@discuss.tchncs.delinkfedilink7•1 month ago everyone understands no, new people learn git every day. ‘main’ is much clearer. It’s maybe not the same readability gain as ‘blocklist/allowlist’ over ‘blacklist/whitelist’, but it’s still there.
minus-square@PotatoesFall@discuss.tchncs.delinkfedilink3•1 month agowe should make the empty string the name for the default branch
Master. I find this out of context fight against words pathetic.
My scrum master said that we need new tickets to update the git branches and pipelines to use main instead of master since master was a bad word.
I asked him what his job title was again and there was a pause.
Then he said we can’t say that we are going to groom the code base anymore.
Switch from your scrum main to your scrum alt.
I’m gonna go ahead and assume your scrum main doesn’t groom themselves.
If we are not grooming the codebase, are we then waxing it?
Or is it more eco-friendly to let the codebase grow wild and untrimmed?
I agree that it’s pathetic. I’ve never been a fan of virtue signaling.
In the other hand, “main” is easier to type than “master” (or “trunk,” for that matter). So I’ve made peace with it.
Trunk would be better because of all the branches.
Why master? main is much clearer
Why not change “walkie talkie” to “radio phone”? It is so much cleaner.
Because change for the sake of change always brings more work than what it saves.
Why change something that works and everyone recognizes it? Of course, if this debate was there when the standard was created…
Because it is a historically settled down terminology that everyone understands and there is no adequate reason to change it.
no, new people learn git every day.
‘main’ is much clearer. It’s maybe not the same readability gain as ‘blocklist/allowlist’ over ‘blacklist/whitelist’, but it’s still there.
Why main? m is much clearer
we should make the empty string the name for the default branch