Live data from Hacker News

Show HN: Hubfs – File System for GitHub

github.com

21–30 of 32 posts

Re: Show HN: Hubfs – File System for GitHub

#21

Very cool! I love using GitHub repos and gists for managing my personal notes/code snippets, and currently use GistPad as an editor-level virtual file system (for VS Code). But having an OS-level equivalent is _super_ useful. Any plans to add support for gists to Hubfs?

Gists are just repos under the hood, it should work natively.

Yeah good point! Though I was also thinking about the ability to easily create/edit/delete gists, by means of file system operations. For example, it would be pretty cool if you could create a directory in some “gists” mount point, and have it transparently create a gist for it. Then, as you add/edit/delete files in that directory, those changes are reflected in the gist’s repo.

Re: Show HN: Hubfs – File System for GitHub

#22

So this is allowing remote git repositories to be treated as a regular filesystem. I really cannot think for good use-cases for this. Maybe to use existing file-based indexing and search tools? I must be missing prime use-cases here.

Like ssh into your server with GitHub actions

Re: Show HN: Hubfs – File System for GitHub

#26

This is cool. I often want to open random files from random GitHub repos in a proper text editor but can't be bothered to pull the whole repository just for that.

If you are signed in, you can hit '.' on your keyboard when browsing a GitHub repo to open it in VS Code in your browser.

Re: Show HN: Hubfs – File System for GitHub

#27

So this is allowing remote git repositories to be treated as a regular filesystem. I really cannot think for good use-cases for this. Maybe to use existing file-based indexing and search tools? I must be missing prime use-cases here.

Your company keeps some things on GitHub but not everyone in the company wants to learn git, the command line, the concepts around git.

Re: Show HN: Hubfs – File System for GitHub

#28
post #13

Earlier quoted context omitted.

Or you could, you know, clone the repository into a local working tree.

Stop for a moment and consider what the tradeoffs of that could be and why it might not work well in some situations.

- Higher latency

- Less efficient use of bandwidth, as the git protocol is optimised for bulk transfers

- Not resilient against unreliable connectivity

- No support for repositories not hosted on GitHub

Yes, I can think of some.

Re: Show HN: Hubfs – File System for GitHub

#30
post #17

So this is allowing remote git repositories to be treated as a regular filesystem. I really cannot think for good use-cases for this. Maybe to use existing file-based indexing and search tools? I must be missing prime use-cases here.

Browsing source code of third party libraries that you're using? This could be especially nice with some debugger integration, if you could just step into a library function, and have the corresponding file opened via hubfs...

Just………clone the repo?
Post reply on HN