Sounds great, feel free to send a PR to change this! We currently use git init hence why master is created instead of main.

@timneutkens Can I work on this one? I'm assuming, this is where I set it to main:

Have created a PR: #17745

git init -b main
error: unknown switch `b'
usage: git init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]] [<directory>]

    --template <template-directory>
                          directory from which templates will be used
    --bare                create a bare repository
    --shared[=<permissions>]
                          specify that the git repository is to be shared amongst several users
    -q, --quiet           be quiet
    --separate-git-dir <gitdir>
                          separate git dir from working tree

Looks like git init does not support branch naming. They have introduced a config option for this though:

git config --global init.defaultBranch main

Sounds like we need to create a new branch then delete the old one if it wasn't main already 🤔

@timneutkens Yes, git init does not support that.. 😕 But however, the branch master does not actually exist initially. The branches get created only when they have at least one commit. Until the branch gets created, the branch only exists in .git/HEAD. So there is no master branch initialized in the repo.

All we have to do is,

git init

git checkout -b main

// now make the commit

In the end, we will have only one branch.

Checkout my PR: https://github.com/vercel/next.js/pull/17745/files