4 ms·
To first order, the network should show up for large projects that have many forks (Sometimes it says "Too many forks to display."). And it should be straightf
by TAForObvReasons 9y ago
To first order, the network should show up for large projects that have many forks (Sometimes it says "Too many forks to display."). And it should be straightforward to distinguish forks with no updates from forks that have diverged from the main repo. Just being able to see forks with changes would be enough in many cases to at least open a conversation with the community.
- jakub_g 9y agoYep, I never found the github "network" thing very useful. The fancy graph is difficult to scroll and analyze. Bitbucket has (for local branches) a simple behind/ahead visualization [1] that IMO would be very nice to have on forks! On top of that, they could integrate something like [2] as I pointed in another comment [1] https://blog.bitbucket.org/files/2013/10/branch-details.png https://blog.bitbucket.org/files/2013/10/branch-details.png [2] http://forked.yannick.io/jquery/jquery http://forked.yannick.io/jquery/jquery