Bug 356643

Description John Crenshaw 2011-09-02 17:06:44 EDT

Build Identifier: 20110301-1815

This is probably related to bug 312586 and bug 302078

Configuring the general Push to Upstream is super clunky for certain workflows and creates various problems when using multiple branches.

1. Pull pulls ONLY the current branch, but there is no easy way to perform a reciprocal operation. Not a problem if you only ever push one branch, but if you share multiple branches, this leads to really frustrating behavior (for example, Push Upstream fails because multiple branches are out of date, you have to go to each branch and pull separately before you can Push Upstream without errors)

2. Pushing new branches is too hard. Currently you have to drill down to a submenu, fill out multiple fields, then press a button to add what you filled out to a list, remove any old stuff that was in the list, and finally push. I just want to push the branch I was on. A menu entry to push the current branch would address this.

3. Configuration doesn't deal with the reality of multiple common push locations that you don't want to always push to (such as a production server.)

Suggested interface/workflow:
1. User uses Team->Push... (Not Team->Remote->Push...)
2. User is shown a dialog containing the following fields: "Repository", "Source ref", "Destination ref". "Repository" is pre-set to the last used repository, "Source ref" is pre-set to the current branch, and "Destination ref" is pre-set to the matching reference in the remote repository if any. Changing the Repository recomputes the Source and Destination fields. Changing the source recomputes destination (as it does on the current Team->Remote->Push... screen).
3. For simple "push my current branch to the usual repository" type operations, the user can immediately click "Finish"
4. For other simple pushes (such as pushing to a production server) the user can change one or more options and click "Finish". (Still easy.)
5. For complex operations, the user can click an "Advanced" button to go to the current Team->Remote->Push... screen

I think the workflow above would resolve both bug 312586 and bug 302078

Reproducible: Always