Community
Participate
Working Groups
In the History view, choose Push Commit... from the context menu and click Next. Now, you can either press Ctrl+Space or start typing a target ref name. Both ways, you are forced to wait until the remote branches have been fetched in the UI thread. The branches would ideally be fetched in the background. But they should at least be fetched automatically when the wizard page is opened, and not only when it's 100% certain that the fetching will interrupt the user's workflow.
+1
https://git.eclipse.org/r/6801
The goal here is mostly to get rid of the blocking popup. An approach can simply be to run the Fetch Job in background and show some eye-candy. Either JGit could reimplement some kind of eye-candy (such has a "Loading refs" label beside the text which would disappear when ready), or use a Dialog with Progress Monitor and do the same hack to keep it usable than what's done in the SmartImportDialog. As I don't think it's so important for user to be able to kill the loading job, I would go for the 1st one which is simpler.
This content assist can be done fully asynchronously using the same mechanisms as in bug 530685.
I believe this issue has been fixed as using I20180308-0630 instead of the UI being blocked I'm seeing a progress monitor on the dialog showing the request being made while I'm still free to type.
Good catch. Yes, this was fixed in EGit 4.11 in the "push-branch-wizard" series of commits[1], which made this wizard page use completely asynchronous ref name content assist. [1] https://git.eclipse.org/r/#/q/topic:push-branch-wizard+(status:open+OR+status:merged)
