Unable to replicate. Is this happening every time you use the CLI? Have you tried using a different package manager?

Hello @nexxeln,
Yes, it also happened when I used npm.
This time I run npx create-t3-app@latest

My git version

Maybe it's something OS specific. As far as I know, zorin is based on ubuntu. I'm also using ubuntu in WSL and works fine for me.

@nexxeln Okay just wanted to let you know about it. It is not detrimental to the creation of the app and someone can manually initialize git themselves. It's an awesome project 👍

Maybe try updating git?

Found the issue, for initialising git we use

git init --initial-branch=main

This is a new feature released in git 2.28 https://github.blog/2020-07-27-highlights-from-git-2-28/#introducing-init-defaultbranch

Working on a fix right now

revert back?

Is commit d2e4d87 considered a "fix" so we can close this? Or should we make it work for older git versions too?

i don't think forcing people to update git to use the cli is a good thing to do though..

I think this was discussed in the server right? that we can just initialise the repository with git init, and then change the branch using git checkout -b main

I think this was discussed in the server right? that we can just initialise the repository with git init, and then change the branch using git checkout -b main

That had the side-effect of leaving behind an unused branch. Wouldn't something like:

const { stdout: gitVersion } = await execa("git --version");
// e.g. gitVersion = "git version 2.32.0 (Apple Git-132)"
const asNumber = ...; // parse the output
if (asNumber >= 2.28) {
  await execa("git init --initial-branch=main", { cwd: projectDir });
} else {
  await execa("git init", { cwd: projectDir });
  await execa("git checkout -b main", { cwd: projectDir }); // maybe?
}

be better?

Yeah. I think that's a better approach, leave an extra branch depending on the git version

Yeah. I think that's a better approach, leave an extra branch depending on the git version

Leaving for work but I can have a PR out tonight.

Is the git --version output the same for every OS? So its parsable the same for all.

Yep, just checked the documentation, pretty sure it's the same command and the same response on every OS

I'm not sure about different versions though, maybe in an old version it was different? But this can just be YOLO'd and fixed as more users report issues

I think this was discussed in the server right? that we can just initialise the repository with git init, and then change the branch using git checkout -b main

That had the side-effect of leaving behind an unused branch. Wouldn't something like:

const { stdout: gitVersion } = await execa("git --version");
// e.g. gitVersion = "git version 2.32.0 (Apple Git-132)"
const asNumber = ...; // parse the output
if (asNumber >= 2.28) {
  await execa("git init --initial-branch=main", { cwd: projectDir });
} else {
  await execa("git init", { cwd: projectDir });
  await execa("git checkout -b main", { cwd: projectDir }); // maybe?
}

be better?

this would be a better approach i think 👍🏼

Got the same problem still with git version 2.25.1. WSL2, Ubuntu.

Initializing Git...
⠋ Creating a new git repo...
✖ Failed: could not initialize git. Update git to the latest version!

Worked with git version 2.37.3