Anton Strogonoff

@crucialfelix > Another approach to this is to use the Relay convention of a top level viewer field. I am thinking of creating a top level 'admin' and 'public' field...

@crucialfelix Seems like a sane way to do it, I might actually adopt the extra nested call too since I’m dealing with staff and non-staff roles. Currently figuring out how...

@parkerault I can reproduce this too. My original issue was with redo, but right now undo is also broken, all invocations after the first one do nothing. It does not...

Might be related to #4854. I have done a few changes as a test, and it looks like undo history gets essentially flushed once it stumbles across the first change...

On second thought, I think it should be possible within react-vtree as is: e.g. I could start fetching data when node is expanded, then once it’s finished update my structure...

Understood. That’s the idea I arrived at in the end: when node is expanded, start data query somewhere else and pass `isLoading` to node component in meantime, then once data...

In our case (large repo, thousands of files in a single directory) each `.add()` call seems to be taking long long seconds to complete. Replacing a loop with `Promise.all(paths.map(…))` doesn’t...

> Or should it provide another object command like `readLfsBlob` that can be used when walking the tree. From end user perspective, I believe there are two typical uses as...

Ran into this too. In my sync logic (which runs only in absence of unstaged/uncommitted changes) I just run pull first to catch any _actual_ fast-forward fails, and then simply...

I’d like to add a note to documentation; but the [errors page](https://github.com/isomorphic-git/isomorphic-git.github.io/blob/source/docs/errors.md) seems to be auto-generated from [GitError](https://github.com/isomorphic-git/isomorphic-git/blob/92a7e8333e1c1565286bb09a178cb8a34e8054ce/src/models/GitError.js). I’d change the message to something like “Push rejected because it was...