Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab default branch name changes to main

about.gitlab.com

Post reply on HN
Print view View original

211–220 of 294 posts

Re: Gitlab default branch name changes to main

#211

Post by easytiger »

oap_bram wrote: post #16

I for one think it's great that people are willing to make things a little more accessible for more people. If people want to be part of our community of developers I think it's great that these organizations listen to people who might have a problem with certain terminology. Even though I don't have a problem with those terms, I think it's still worth evaluating if they're worth keeping if it makes it harder for som…

> I for one think it's great that people are willing to make things a little more accessible for more people.

This doesn't achieve that. It very clearly does nothing.

Human beings as basic pattern matching engines have been hacked by things like twitter to amplify beyond reasonableness many concepts and ideas which they are shown as related and then regurgitate and spread.

Whilst this in particular may not be "important" it is certainly but one minor example of a very serious trend that is demonstrating a very low latency mechanism at play for creating fast paced change in western society that undermines the strengths of slow change that made it so successful.

Now you might be the kind of person who might have a desire to see those fundamentals undermined under a guise of faux altruistic reasonableness, I don't know, but the overly simplistic acceptance of it indicates an avoidance of any of the reasons why people might be resistant to it. Thus why i question your motivations here.

Re: Gitlab default branch name changes to main

#213

Post by dvdgsng »

devnull255 wrote: post #202
macspoofing wrote: post #158

Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…

If you dig a little deeper you might find your brain does make that kind of connection subconsciously. This article gives a nice introduction into the work of cognitive linguists George Lakoff and Mark Johnson. https://theconversation.com/how-did-white-become-a-metaphor-... . The language constructs we use embed positive and negative associations with the words used to describe black or white things, low or high conc…

> your brain does make that kind of connection subconsciously

This should work both ways then. So loving black tea, black humor, Black Mirror, Black Swan and the color black in general would make me like "black people" more because my brain does the wiring subconsciously when it reads the term "black"? Nope. Don't think so. But maybe making everything about race is, well, racist?

Re: Gitlab default branch name changes to main

#214

Post by dvdgsng »

franky47 wrote: post #60

Since we're talking about naming branches, what are your preferred names for branches ? I like 4-letter names: - `main` points to the last release for libraries (along with tags for history) - `prod` points to production in deployable projects (not libraries) - `next` is the development branch for the next version - `deps` is a temporary branch for dependency updates, squashed and merged regularly onto `next`

Good for you that you found something that works for you. But why the random length restrictions to 4 chars, seems kind of outdated? Also, how does using only a "next" branch for development scale for teams (maybe using a fork-based workflow?).

While I use a similar approach like yours on my personal projects, I still prefer the widely known and battle proven Git-Flow when working on agile teams:

    - master
    - develop (optional)
    - feature/*
    - release/*
    - bugfix/* (optional)
    - hotfix/*

Re: Gitlab default branch name changes to main

#215

Post by scrollaway »

macspoofing wrote: post #158

Yeah, I get it. It is a necessary change just so you take this of the table and not deal with the sporadic complaints that would come. Keeping the 'master' or 'master-slave' (in context of HA) terms just isn't worth potentially offending someone, or losing a sale, or getting bad press. We changed our verbage a couple years in our product as well just for that reason (Master-Slave to Primary-Secondary). The previous c…

I don't mind so much when the renames make sense or are more comprehensible… master to primary for DBs, master to main for git. Indeed whitelist/blacklist is just ridiculous overreach, what can you do.

But Github went way too far by aggressively pushing devs to rename their own local master branches to main. This caught me by surprise and I almost accidentally renamed the branch of one of my previous clients.

https://twitter.com/Adys/status/1354468440753508355

Really gross.

Re: Gitlab default branch name changes to main

#216

Post by benibela »

naebother wrote: post #172

If we must have a struggle-session on this and rename to appease the performative gods, why not just call the default branch, you know, "default"?

Yes, this is such a silly Git problem

In Mercurial it is always "default", and in SVN one used to use "trunk"

Re: Gitlab default branch name changes to main

#217

Post by totony »

ec109685 wrote: post #170
gher-shyu3i wrote: post #135

Earlier quoted context omitted.

How is blacklist and whitelist offensive now? It seems that some people have nothing better to do than make trouble for the sake of it.

It reinforces black is bad and white is good. Also, deny list and allow list are more precise terms anyway.

>Also, deny list and allow list are more precise terms anyway.

Are they? Black/whitelist feels way more natural to me. You can also say things like "blacklisted this ip" instead of "adding to the deny list" or something.

Re: Gitlab default branch name changes to main

#218

Post by noxer »

elric wrote: post #48

I would like to point out that it's perfectly OK to have master/slave relations between computers, hard disks and git branches. The only place where it's problematic is between humans. Perhaps we would do well to remember that words can have different meanings in different contexts. It's nice to try to be considerate of people who are sensitive to certain issues, but at the same time they would do well to limit their…

Its perfectly fine between humans as well. The difference between humans an machines is, one can and should give consent the other not.

Re: Gitlab default branch name changes to main

#219

Post by africanboy »

ec109685 wrote: post #170
gher-shyu3i wrote: post #135

Earlier quoted context omitted.

How is blacklist and whitelist offensive now? It seems that some people have nothing better to do than make trouble for the sake of it.

It reinforces black is bad and white is good. Also, deny list and allow list are more precise terms anyway.

blacklist was never intended to mean black people, but undesired people

it doesn't reinforce the idea that black is bad and white is good, it was modelled around the idea that black is bad and white is good.

Because for humans black (dark) is bad and white (light) is good.

Black cats were considered a symbol of bad luck because they were invisible in the dark, not because they resembled black people.

Re: Gitlab default branch name changes to main

#220

Post by swiley »

cmckn wrote: post #6

I think the default branch name change has been good for the ecosystem; “master” didn’t always make sense for whatever workflow was used, and it was hardcoded all over a bunch of tooling. I think “main” makes more sense, regardless of politics, and this encouraged a lot of software to make the default branch configurable.

The workflow I use on my personal repo (for stuff I can't/won't publish) doesn't even use a default branch, just feature branches and branches named after hostnames.
Post reply on HN