3 ms·
OK, the main page lacks information. https://www.presslabs.com/gitfs/docs/usage/ https://www.presslabs.com/gitfs/docs/usage/ https://www.presslabs.com/gitfs/d
by leni536 11y ago
OK, the main page lacks information.
https://www.presslabs.com/gitfs/docs/usage/ https://www.presslabs.com/gitfs/docs/usage/
https://www.presslabs.com/gitfs/docs/arguments/ https://www.presslabs.com/gitfs/docs/arguments/
So apparently you can mount remotes, not only local .git dirs. This is really handy and it should be listed on the main page, really.
I raises an other question: can I mount remotes where I don't have write access read-only?
For the directory structure the history directory makes sense for mounted projects that are edited with gitfs. For other projects, not so much. What about having a read only tags/ and commits/ directory too?
- vtemian 11y agoI agree, the main page is a little bit outdated. You can mount remotes with where you have only read access, gitfs will fail to push something on the remote, and will put the entire repository in read-only. Right now, you don't have a read-only option, but it would be nice to have :) Great idea about tags and commits directories. It would be nice to specify at mount point, if you also want tags and/or commits etc. You can fork it https://github.com/PressLabs/gitfs https://github.com/PressLabs/gitfs and start hacking around.
- leni536 11y agoThanks, an other question: what happens when the remote can't fast-forward merge? I assume it doesn't force push.