Git proper doesn't have that kind of read granularity by virtue of the distributed and decentralized nature of the repository. Even though Gitlab allows for a centralized repository, there is no model available to control read access to certain parts of a repository tree. Your best bet is to either put the sensitive information into separate repositories and use git submodules to reference the other repositories in your main repository.
-Alex On Fri, Aug 15, 2014 at 11:35 PM, Alex Ramos <atra...@gmail.com> wrote: > I employ freelancers to maintain a large website. In order to protect > Intellectual Property, I prefer to limit access to only the files they need > to do their job. Does GitLab support a setup where developers can be > granted access to only certain files? > > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/2f303177-44dd-4776-8181-06467196c26b%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAGWx_yY_aQ_Sh7hSikSyEH3Qobkppz5KXVjVKSF6%3DJU8Ug3XWg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
