You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a browser-based git client using isomorphic-git, and noticed a couple of differences here against the official git client:
With the official git CLI, git init --separate-git-dir=foo creates a .git text file containing gitdir: /repo/foo/. isomorphic-git does not do this.
If this git init is run inside an existing repo directory, the git CLI moves the contents of the gitdir to the new location, whereas isomorphic-git does not do so.
For the second one, it's possible that isomorphic-git just doesn't handle git init in an existing repo at all, but I'm not far enough with my client to know if that's the case. 😅
Neither of these is a big issue (because who even uses a different git dir?) but I thought it was worth reporting anyway. 🙂
I'm using isomorphic-git in the browser, bundled using rollup.
The text was updated successfully, but these errors were encountered:
I'm developing a browser-based git client using isomorphic-git, and noticed a couple of differences here against the official git client:
git init --separate-git-dir=foo
creates a.git
text file containinggitdir: /repo/foo/
. isomorphic-git does not do this.For the second one, it's possible that isomorphic-git just doesn't handle
git init
in an existing repo at all, but I'm not far enough with my client to know if that's the case. 😅Neither of these is a big issue (because who even uses a different git dir?) but I thought it was worth reporting anyway. 🙂
I'm using isomorphic-git in the browser, bundled using rollup.
The text was updated successfully, but these errors were encountered: