Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] making push force more handy

On Fri, Jun 14, 2013 at 3:38 PM, André Dietisheim <adietish@xxxxxxxxxx> wrote:
Hi

I'm currently looking into improve EGit here and there usability-wise (and in my daily job). We have master repos on github and each dev has its personal fork. We all work on topics-branches. Once the code is ready we rebase (or amend beforehad) and file a pull-request which then gets merged into the master repo.
The git staging view is just awesome, it allows commiting and pushing to my github fork in a single (button) click. That's even easier than on the cmd-line. Unfortunately when I amend, I have to push force to my fork which is not as handy.

* The git-staging view doesn't offer a force switch which could come very handy but could also be very dangerous. What are your thoughts?

yes, it's dangerous, we could add a force switch but it's default should be always off.
Maybe we should only offer it after fast forward failed.
 
*  Team->Remote->Push needs one 1 click too much: it doesn't come preconfigured. You have to select your local branch, add the refspec and check "force". I'd prefill the local branch. That would safe 1 click and would things slightly more handy. Thoughts?

that looks like a good idea
 
* Team->Push To Upstream wont allow me to push force. Invoking it will tell me that my push is of course "non fast-forward". The only option I have there is to "Configure..." but this will change my repo-configuration and this is not what I want to do. I only want to push force this single time (and eventually another time later on). What about offering "Push..." there, too?

push to upstream is meant to be single click for the most frequently needed case.
Why don't you trigger Push... from the repositories view ?

--
Matthias

Back to the top