Stefan Bourlon

@ephesused @kargakis I can confirm this bug simply by following the example in [Using Afero for Testing](https://github.com/spf13/afero#using-afero-for-testing). ```golang package main import ( "fmt" "os" "github.com/spf13/afero" ) func main() { appFS...

Hi @saracen, thanks for the PR. Could you share your fixtures?

thank you @saracen I am available to test any change if you need. So far, what I did: ``` # clone my fork of go-git GO_GIT_PATH="$HOME/Documents/src/git/github.com/sbourlon/go-git" git clone [email protected]:sbourlon/go-git.git "$GO_GIT_PATH"...

@saracen I sent you a PR fixing the gitdir of worktrees (https://github.com/saracen/go-git-fixtures/pull/1). Now the tests are passing: ``` % go test . ok gopkg.in/src-d/go-git.v4 34.107s ```

thanks @saracen, doing now.

@saracen the tests pass, however it is not working in my case because I am using the `Open` function instead of PlainOpen. Would it be possible to read the dotGitCommonDirectory...

My use case is to run the same command as: `git --git-dir=../remote-worktree/.git commit` What about updating `NewStorageWithOptions()` (https://github.com/src-d/go-git/blob/master/storage/filesystem/storage.go#L46) to detect the commondir from the `fs` argument?

I need to pass both the work tree dir and the gitdir because they are located in different directories. Here is an interesting article explaining that: https://www.logicbig.com/tutorials/misc/git/custom-git-dir.html In the git...

thanks @saracen, I was able to reset my linked worktree to the main worktree, however I think `PlainOpen()` sets the worktree to the linked worktree's worktree, which is different than...

it's finally working! I will sent you a small PR to load a separate worktree tomorrow morning (PST time) Thanks again @saracen for your help.