Re: Git "branch properties"-- thoughts?

>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

Re: Git "branch properties"-- thoughts?

Phillip Wood writes: > It would certainly be nice to be able to share branch descriptions so > that if I clone a repository I can get a bit more detail about the ideas > behind each branch. Shared descriptions could be displayed in web uis. I One thing to note is that

Re: Git "branch properties"-- thoughts?

On 22/02/18 18:29, Paul Smith wrote: > > Hi all. I'm wondering if anyone has any thoughts about the best, or > even any, way to have "branch properties": some extra information which > is attached to a branch (that is, the actual branch name not the commit > it currently points to). > > My

Git "branch properties"-- thoughts?

Hi all. I'm wondering if anyone has any thoughts about the best, or even any, way to have "branch properties": some extra information which is attached to a branch (that is, the actual branch name not the commit it currently points to). My requirements are that the information needs to be pushed