So creating a new repo on GitHub, you get a set of getting started steps. They changed the default branchname to “main” from “master” due to its connotations with slavery.
When I create a new repo now, the initial getting started steps recommend creating a branch named “master” as opposed to “main” as it was a while ago.
It’s especially weird since the line git branch -M master is completely unnecessary, since git init still sets you up with a “master” branch.
Disclaimer: I have a bunch of private repos, and my default branchnames are pretty much all “master”.
Is this a recent change?
Edit: Mystery solved, my default branchname is “master”. Thanks bamboo@lemmy.blahaj.zone !
colloquial terms? these are terms that describe technical standards that have likely been around longer than you’ve been alive.
Imagine if your doctor one day said you have rectumbabados instead of colorectal cancer because the word “cancer” is too triggering.
that’s the problem with young inexperienced devs these days. they just don’t get it. standards aren’t meant to change. standards are meant to adapt and evolve. forcing a frivolous name change on a branching strategy all for corporate to check their “social responsibility” checkbox is not evolving. it’s not adapting. it’s corporate grandstanding and literally is meaningless. like Target saying they support LGBTQ+ and then yanking all DEI support.
I maintain enterprise solutions. I hold myself to a higher standard than you might and have proven my worth through consistent delivery. my builds take minutes. my deployments take minutes. my counterparts take an hour or more to build and deploy. if I were to do whatever the fuck you’re doing I would be out of a job.
get some real experience before you go hotdogging with that tiny wiener you call expertise.
Again, you’re conflating your own stubbornness with correctness and that just ain’t how it goes. Branch names are frivolous. So much so that changing the strategy or retargeting a branch one time shouldn’t be such a nightmare for your pipelines that you have to pretend like you’re the big dick on campus spouting accomplishments when someone mildly suggests there’s a mistake in your thinking. Look inward if you’re so upset by this that you have to make up irrelevant insults in a vague attempt to protect your own ego, then go fix your pipelines to make it easier to do for the next person after you’re gone.
I’m not confused but you seem to be. you were the one coming out swinging.
that was you, yes? you seemed mad. some advice, don’t go pissing on people if you don’t want to get pissed on.
if branch names are frivolous then why change them at all? why not keep it as master if it doesn’t matter? you seem to be conflating two conflicting streams of thought, are you ok?
I’ll show the math from another comment I posted just to show the true cost of a “simple change”.
btw, that’s dedicated work. no other projects get done in those hours.
then we have blowback. things like, updating documentation, training the rest of the team on using main over master, correctly attributing PRs to main over master, updating local scripts that may be referencing master, updating local repos that have master set as origin, etc…
how many hours will a company allot for tech debt? in theory, 10% of the sprint. in practice, 1%.
so now because of a “simple branch rename” we’ve reduced output, delayed delivery, increased error rates, increased confusion, increased stress. all for what?
a frivolous name of a branch, was it?
I think I’ll keep master around. you want to lose your job because you want to waste your time, go for it!