Short version:
You need to use a separate repo on the top-level folder to which you want to grant access. See submodules for more information on how to do this.
"rare" checks may work, but I believe that this cannot be imposed on your users, who in any case should clone the entire repository to the local one, and then just get an incomplete working directory.
(You can also set up a separate repo that will automatically update and push changes to it, but you lose the ability to combine forks and corrections from your user base, which seems to be the point.)
Longer version: Wo "New" distributed version control systems (Git, Mercurial, Bazaar, etc.) Not built to check each folder in the same way as SVN and CVS. Having a branch tree separate from the directory tree simplifies branch processing and merging in the revision graph, since they are more numerous than for centralized VC: es. (SVN, IMO, processes branches and merges like a sledgehammer, processes a jar of spam, most of this is due to the fact that any directory in the hierarchy can be branched / merged).
The function of partial checks is easy to give in centralized scenarios, where you do not do branching / merging, and therefore are popular at dawn. You donβt understand this anymore and probably learn to be thankful for not receiving it. :)
Thus, facilitate several subrepositions / submodules of important material. Branching the top repo is a bit more complicated, so you need to think about how you want to tune the situation to make your job easier. (Maybe releasing presentation slides isn't that bad? :)
Macke source share