Improve the UX of an always Commit+Push workflow

[Caleb-T-Owens]

Based on the following conversation on discord:

Kenneth Y. — Today at 18:19
Is there a “commit and push” button?

Caleb Owens — Today at 18:25
Commiting and pushing are currently two different actions; Once you've made a commit to a vbranch, you should see a button with a little dropdown next to it. By default it should say "push to remote", but if its saying "create a <draft> pr", you can use that dropdown to choose the "push to remote" behaviour.

Kenneth Y. — Today at 18:30
Ok cool. It would be nice if there would also be an option to do commit and push at the same time. Or have a keyboard shortcut for the action. I can use ctrl/cmd + enter to commit so it would be be cool to also do the same for push

Caleb Owens — Today at 19:26
That has been something I've thought about because there have been a few times I've hit cmd+enter twice with the expectation that it would commit and push.

We would need to carefully consider how it behaves with it being a three state button though; we don't want you accidentally creating a PR.

I'll create a GH issue for this topic

Kenneth Y. — Today at 19:30
IntelliJ has two buttons by default: commit and commit + push. You use cmd+enter for commit only and option+cmd+enter to commit and push. That’s one potential model. I happen to subscribe to the workflow of always pushing commits to your branch and never leave anything to be local only

Improve the UX of a Commit+Push workflow.

It would be interesting to explore combinations of having a commit and commit+push button, having keyboard shortcuts, or perhaps having an "always push" mode which would always push any changes if they don't require a force push.