This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 250408 - Push dialog: Show number of incoming/outgoing commits per branch too
Summary: Push dialog: Show number of incoming/outgoing commits per branch too
Status: NEW
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Git (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Ondrej Vrabec
Depends on:
Reported: 2015-02-13 09:51 UTC by markiewb
Modified: 2015-07-15 13:05 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description markiewb 2015-02-13 09:51:59 UTC
Git push dialog:

ACTUAL: Currently there are shown only colored labels like [A] for added, [U] for updating... The tooltip per branch translates the abbreviations [A]/[U] to a long descripteion

EXPECTED: if possible show the number of incoming/outgoing commits per branch too
Comment 1 markiewb 2015-02-13 09:52:35 UTC
If it is too much consider to show that information in the tooltip
Comment 2 Ondrej Vrabec 2015-02-13 10:29:55 UTC
To display the absolutely correct info may be too expensive - requires to fetch all branches along with all their commits and objects.
Instead it may be enough to display just the difference between local branch and remote tracking branch (aka master vs origin/master).
Comment 3 hifi 2015-07-15 12:32:57 UTC
We've had this interesting incident where the remote branch was --hard reset a lot back because of accident push of wrong commits. After the reset, everything was fine for a day until someone who had already fetched the accident did some more work on it pushed all of the faulty commits back and one fix.

It's a workflow and communication issue this happened, but it was impossible to know for the pushing developer he was pushing 21 commits instead of just one because the push dialog never showed any indication of that.

So in the push dialog, like commented by Ondrej, you could at least show in the final page after you have selected which branches etc. you're going to push the difference of commits. In this case it only works if there's an implicit fetch of the selected branches in-between so you get accurate information (also about conflicts).
Comment 4 Ondrej Vrabec 2015-07-15 13:05:55 UTC
(In reply to hifi from comment #3)
Do you use the push wizard? To be honest i have not used it a while, instead i periodically run Push to Upstream which is much faster.
So unless all your developers use the wizard, your problem will not be solved with fixing this issue. But sure it would be at least something.

I think your scenario rather needs something such as this:
Push to Upstream -> before actually pushing the IDE would have to compare origin/BRANCH to the BRANCH in the remote repository and in case BRANCH is not descendant of origin/BRANCH it could give a warning.