[xorcist]

Read access can't really be partially restricted in git, because git is content addressed. Without the data you can't construct the sha hash, so there's no way to address a commit at all. You could publish partial data, and you could generate new partial commits for that data, but it would probably not be very useful outside of a very niche use case.

[rcxdude]

with the sparse checkout/partial clone features there's no particular reason you couldn't enforce partial read access: the way git tree hashes work, if you don't change anything in a subdirectory, the contribution of that hash to the tree doesn't change. So as long as you have the hash of that directory you don't need the contents to construct a new commit. The same is true for files themselves: the main thing that must be known is that if you are a file you must know the contents of it, and the directory listing of all the parent folders up to the root. Everything else you only need to know the hash. This is how sparse checkouts work and still allow commits, and it can be turned into partial read access by only allowing sparse checkout and not allowing the content of those directories to be sent to the client.

[nsteel]

Thanks for this excellent explanation. I'm not aware of any software that makes this easy e.g. like gitolite or gitlab but I'm pleased to now realise this isn't because it's not possible! I think there would be a lot of value in someone providing this feature.

[xorcist]

That is true! I forgot about that. You need to be able to read metadata, including file names, but not the actual contents as the hash would suffice. That sounds like the start of quite a fun project!