`git.init()` with `gitdir` set behaves differently to `git init --separate-git-dir=foo` about isomorphic-git HOT 3 OPEN

Isomorphic-git's init({gitdir:<path to gitdir>}) doesn't quite behave as Canonical Git git init --separate-git-dir=<path to gitdir> .
Canonical Git, creates a .git file with a link to <gitdir>. While isomorphic-git just directly creates <gitdir>, and you have to pass it for each subsequent command.

I'm curious what's your use case for supporting --separate-git-dir ?

from isomorphic-git.

I'm curious what's your use case for supporting --separate-git-dir ?

The use case is roughly "copy canonical git's command line and functionality". You can find the app here: https://github.com/HeyPuter/puter/tree/main/packages/git It's part of a whole cloud OS, and the idea is someone could use it from Puter's terminal just like they would on any other OS.

from isomorphic-git.

@hhourani27 I think that git.init({gitdir}) is creating a new git bare repo, not changing the git directory. It's by design.

from isomorphic-git.