I was just wondering if other people working in a team using github for private projects had the same kind of Network map ?
Or are we doing something obviously wrong ?
I was just wondering if other people working in a team using github for private projects had the same kind of Network map ?
Or are we doing something obviously wrong ?
I don't know if your network graph is common amongst other GitHub projects, but it has only only one issue:
The main reference line (top block one) is not linear.
Meaning anyone pulling from it some time ago is likely, when he/she finally update its local copy, to apply the "RECOVERING FROM UPSTREAM REBASE" paragraph if they want to apply their local work on top of the new history.
Other than that, long-lived branches (like the bottom red one) are always harder to merge (but off course, much easier than with Subversion).
Nothing major though.
Well I kind of had the same concern with my team's network map looking something like yours and wasn't sure how all the local branches showed up there. I got a nice and detailed answer to my question HERE as to where all that clutter appears to be coming from. Other than that you don't need to worry too much about how the map looks, you've got to stick to a workflow that works for your team and don't be afraid of experimenting.