-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.15.1869 push to remote buttons disabled unless on remote #318
Comments
👍 Yeah, this is killing my workflow too. |
Workaround: use the gear icon to the left of the cloud icons. Select the Push master to > origin (or whatever other branch/remote you want. |
Is this affecting the context menu on the sidebar, or on the ref labels in the history view? |
Both the sidebar context menu and the ref label context menu still have options for Push (Boy I really miss the "shortcut" entry for pushing a ref to the default (or only?) remote that used to live in the top level context menu. It seems like if there is only 1 remote, the submenu is hit to productivity, having to wait even a half-second for it to open.) |
This was caused by my change to the latest objective-git API, which (during my fix to accommodate their changes) broke the lookup of which was the tracking branch for a given ref. Since I use "push to -> remote name" from the refs menu, this slipped past. Should be fixed in the upcoming build. |
The push to remote button os disabled unless I click on the remote site, in which case it doesn't know what branch to push. Back to using the command line.
The text was updated successfully, but these errors were encountered: