>But for a generic branch like 'master', that arrangement would not >work well, I am afraid. You may have N copies of the same project, >where the 'master' branch of each is used to work on separate topic. >The focus of the 'master' branch of the overall project would be >quite different from each of these copies you have, hence it is >likely that it would be inappropriate to share the task list and >stuff you would want to add to branch descriptions and branch >properties between the shared repository's 'master' and any of your >'master' in these N copies you have. > >So... I think it could work in a way that other people branch properties are only taken into account if you don't have your own properties of those same names already set. In that case, git would initialize your branch properties from the other branch of the same name and inform you about it. Of course, you should always have a way to overwrite any property to a value of your choice. So what you would be getting from others were basically default values (inspired by https://docs.python.org/3.5/library/stdtypes.html#dict.setdefault). Would it work? This sounds pretty good to me. I would really love to have a chance to implement this feature if people were interested in it. clime
