For consistency and summary in sidebar, show the number of branches and remotes as well #1306
Comments
|
I don't think this is necessary.
|
|
I disagree rather strongly - it's much more consistent to have the count displayed on each category. I'm always frustrated when UIs fail to present the number of items in a list, making me have to count them manually or look elsewhere for the count. (We have a lot of branches and tags in our main repos, so a count is definitely needed.) Also, the count is very useful when a category is collapsed, since you don't have to expand it to see how many items it has. But, since we have different opinions, surely this could be made a Preference option ("Show item counts in sidebar" or similar) ? |
|
BTW, the number of Branches under each Remote may also change after fetching. Displaying the number can make it more convenient for users to know that new branches have been pushed (or old ones pruned). |
|
NOTE: The count of branches should be the "flat list" counts per Local/Remote (rather than the count of root-items from the BranchTrees lists). |
|
Done.
|
|
This is perfect! Now there are even counts on the branch "parent-folders"! 💯 Thank you, @love-linger! |
|
Oohh... Missed a spot - for consistency, we should now do the same for "parent-folders" under TAGS (when enabling
|
Signed-off-by: leo <longshuang@msn.cn>
|
Done |
|
Thank you, that's excellent! And don't get mad at me now, but I found one more place where we can be more consistent with counts. 😅 We show a count (badge) for LOCAL CHANGES, but we could similarly show the count of CHANGES in the selected history-commit...
|
No. Please do NOT change the others. This has nothing to do with |
|
The thing is, we show the count of Unstaged and Staged changes, and the total count of Local Changes. It WOULD be consistent to show the count of Changes for a historic commit SOMEWHERE (doesn't have to be on the "tab" itself). My point is, that when there's a potentially long list (of varying size) we shouldn't have to count hundreds of items "manually" to answer the simple question of (for example) "how many changes were there in this commit". Our earlier VCS was Plastic SCM, and their UI does indeed show the count of changed items for historic commits. It is not far-fetched. (Plastic even shows separately the number of Changed / Added / Deleted / Moved files, which is great...)
GitHub Desktop shows the number of changed files when looking at historic commits. They do it just above the list, which makes perfect sense:
Similarly, in GitHub on the web, the number of changed files (along with the total number of lines changed) are displayed at the top when visiting a commit from history:
|
The left sidebar shows the number of Tags, Submodules and Worktrees, which gives a good quick overview / summary.
We could add a similar counter for the number of Local Branches, the number of Remotes and additionally for the number of branches on each remote. This would be more consistent and would give at-a-glance info even when the corresponding category is collapsed.
The text was updated successfully, but these errors were encountered: