{"thread":{"id":"50640","subject":"Git Monorepo","startedAt":"2019-03-04T12:42:43Z","lastAt":"2019-03-04T12:42:43Z","messageCount":1,"participants":["Sandu Turcan"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"370598","messageId":"CAEnBgA0=F8rDkUJEy-nUYGuqPMvMW1XwkAg=B8uN9yDTQtzRMA@mail.gmail.com","threadId":"50640","inReplyTo":null,"subject":"Git Monorepo","fromName":"Sandu Turcan","fromEmail":"idlsoft@gmail.com","sentAt":"2019-03-04T12:42:19Z","receivedAt":"2019-03-04T12:42:43Z","isPatch":false,"sender":{"key":"idlsoft@gmail.com","avatar":null},"body":"At my company we need to be able to manage access to different parts\nof source code.\n\nWe've used separate git repos in the past, but then discovered\nMercurial’s narrow extension, which supports sever side filtering.\n\nWe all clone one repo, but get different subsets of the source, based\non permissions.\nIt’s pretty seamless, and works well. There are some limitations, like\nnot being able to merge files outside your filter, but on balance\nthings are easier to manage.\n\nI'm trying to see if the same can be done with Git.\nThe latest version seems to have some ingredients, like sparse\ncheckout, and blob filtering. They're both meant to address\nperformance AFAIK, but perhaps can also be used as foundation for\nimplementing permissions.\n\nI have some ideas on how this would work, and my company is willing to\nsupport the effort, but we'd like to coordinate it with git\ndevelopers.\n\nThere have been a number of attempts to implement a git monorepo over\nthe years, I'm sure it would benefit a lot of people.\n"}]}