Has Github/Microsoft rolled back the master to main switch?
-
[email protected]replied to [email protected] last edited by
Honestly I feel like people who had an issue with this were just as much making an issue out of nothing. I personally also think that "master" is just as much a normal and valid name as "main", and to me the rename kinda felt like performative bullshit. But at the same time it's just a name, if it makes people happy I don't really care either. Nowadays I tend to use main, but it's not something I really pay attention to.
-
[email protected]replied to [email protected] last edited by
Do you speak french too? I'm french myself and we use master for so many normal things. Americans don't get that word right because their langage lost many of its meanings. It's funny to see people get offended just because they misunderstand the etymology of a word
-
[email protected]replied to [email protected] last edited by
quite frankly it doesn’t matter
In that case, the name of the branch shouldn't matter. Why are you arguing so hard that it does?
Computers used to have a literal slave/master relationship with hardware components and control systems
OK, this part is just utter nonsense.
-
[email protected]replied to [email protected] last edited by
nailed it lmao
-
[email protected]replied to [email protected] last edited by
I appreciate your intense emotion about the topic of changing terminology. It's hard to wrangle in our feelings when things change.
I completely agree with your last statement. What have you done to accomplish that?
-
[email protected]replied to [email protected] last edited by
my editor converts tabs to spaces and back again. so that's a non-issue.
I do put personal preference ahead of what the group wants if the group wants something that has been called "frivolous" and "not that big of a deal".
I don't understand how I'm the asshole if I'm the one made responsible for setting the standards for the team.
-
[email protected]replied to [email protected] last edited by
what's hilarious to me is none of you realizes that I might not be white. you've judged the color of my skin entirely based on an opinion that conflicts with your perception of what a person of color would have. last time I checked that's racial profiling, which is racist. so...who's trying to impose power over whom here?
regardless, I vehemently deny that I want to use "master" to force my will onto others (outside of maintaining a standard branching strat). as I have stated previously, the hourly cost to convert master to main is far too high to consume and too frivolous of a change to piecemeal out over the next three years.
until HR is ready to explain to the executives why I can't deliver the features they want this quarter, it'll stay as "master".
-
[email protected]replied to [email protected] last edited by
-
The stupidest problem I've seen arising from this debate was that with one employer they had a legally required retention policy, and instead of implementing it in their GitLab server software, they did it directly by coming in between GitLab and git. The result was that they had no idea which to use, so they protected both.
On one repo, we mistakenly made both branches, and there was no way to get rid of either, so it kinda just stayed there. It confused the hell out of new people.
-
[email protected]replied to [email protected] last edited by
That might be it then. I never really read the getting started guide.
-
[email protected]replied to [email protected] last edited by
You mean the GitHub account? It's my personal one, 9-10 years old I think.
-
[email protected]replied to [email protected] last edited by
It’s funny to see people get offended just because they misunderstand the etymology of a word
I've got a story for you then:
-
[email protected]replied to [email protected] last edited by
How about trunk to imply how to use it
-
When's the time you changed branch names after creation? Master to main is the only time for a lot of devs