On Aug 5, 2021, at 9:56 AM, David Frenzel <david.fren...@t-systems.com> wrote: > > What you can do is host a Git server instance e.g. on Linux for Z. This way > you don't have to move your assets off the machine. > If moving something off the platform is not the concern but rather who can > access it then I'd suggest to restrict the repositories to the people that > need to know. GitHub for Enterprise allows you to do exactly that. You can > setup teams/organizations which have specific access to repositories and > projects. > > You'll have to answer the question on how you keep these assets in sync. In > the end you would want to deploy your assets from Git to the actual Parmlib > but I assume that this will be quite difficult to achieve.
Right. I don’t know of any way to use GitHub Enterprise without having clones of the repositories present in GitHub E, but it’s fairly easy to restrict which GitHub E users can see your repositories. -- Pew, Curtis G curtis....@austin.utexas.edu ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
