From my point of view nothing should stop developers from adding this feature, since anyone who don't like it would use first nested level. Another key point: it may be very useful when organization is huge and there are a lot of different teams working on set projects, so you can reflect that in group hierarchy. However this can be done in other way: by using tags for git projects instead of group hierarchy
From my point of view nothing should stop developers from adding this feature, since anyone who don't like it would use first nested level.
Another key point: it may be very useful when organization is huge and there are a lot of different teams working on set projects, so you can reflect that in group hierarchy. However this can be done in other way: by using tags for git projects instead of group hierarchy