@patricia@mastodon.social Huh, master is still the git default when creating a repo. Its only some services like github that have non-standard defaults... It seems new projects created using git on the command line (the way most pros do it) will still tend to use master over main.

@freemo @patricia Where's your data on “the way most pros do it” coming from?

@bjorn

Just personal experience. Vast majority of pros seem to use git command line and not through a gui. They use github of course, but only as the server repository not to replace the command line. I dont think ive ever seen a pro actually edit or modify their git repo through the github web IDE thing.

@patricia@mastodon.social

@freemo @bjorn @patricia This has nothing to do with modifying repo through web IDE vs CLI.

When *creating* repo on Github or GitLab, the default is `main`, so once you clone it to start working on it locally, that's what the main branch will be called.

The only way you get the old / locally configured default is if you create repo locally first, then create it on the remote host, and then push & set upstream - but that's just more work compared to the approach above and hence less common.

@rreverser

Yes itt happens on creation. My point is usually people who use github to work with git are the ones seeing this.. The pros use the command line to work with git including creation of their repos..

The reason i find local creation most common is because people dont usually create their github repo day one. I usually find people start working locally until a few commits in and only then create a github repo and push.

Whatever the reason I just know I see master default branches on new projects far more often than I see main right now.

@bjorn @patricia@mastodon.social

@freemo @bjorn @patricia

> I usually find people start working locally until a few commits in and only then create a github repo and push.

Sounds like people not taught by life to backup from the start.

This whole exchange sounds a lot like xkcd.com/378/. You seem to be defining "pros" based not on their ability to keep up with changes in tech, but based on expectations of them using the "more technical" or "cooler" tools - from command line all the way to butterflies.

Follow

@rreverser

I am defining pro as a person who has expert level understanding of the git tool, nothing else. The fact that such people usually use the command line tool and not a web interface is secondary to that.

@bjorn @patricia@mastodon.social

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.