I see. I'll go with two separate repos and then do some script/alias work to get the "transparency" effect. Thanks for the explanation.
Br, Morten On Aug 27, 8:34 pm, Tekkub <[EMAIL PROTECTED]> wrote: > Hrm... that's most of it, but I don't think a submodule will work if you > only want *some* people to have access to it. You should probably just > include a script "thingy" that clones the other repo into the path you want, > and add that path to the base repo's .gitignore so that the files never get > committed into the base repo. > > A script wouldn't be "transparent" though, the user would have to run it to > setup and then run git-pull inside that repo... but with submodules they > would have to do the same (`git-submodule init` and `git submodule update`) > > --tek > > On Wed, Aug 27, 2008 at 12:24 PM, Morten <[EMAIL PROTECTED]> wrote: > > > Hi. > > > I need to grant some external developers access to some source code. > > There is some sensitive information that they should not be able to > > see. > > > How to do this? I'm thinking: > > > 1. Shallow clone of current repository > > 2. Modify/remove files > > 3. Copy edited set into new repository without history > > 4. Give access to this repository > > 5. Create a submodule with sensitive data > > 6. Make a "thingy" to pull the submodule when the puller has access to > > it > > > Would this work? Any better suggestions? Any tips on how to accomplish > > #6? I'd really prefer to make this setup run transparently so I don't > > need to merge back and forth.. forever... > > > Thanks! > > > Morten --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
