[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] making push force more handy
|
I agree that forced push is a dangerous command, therefore I would
never add it to the context menu. Moreover, I don't even think this
option (wherever added) should be persisted, allowing to push force on
the next run. At the same time, we should allow to use it (add a
checkbox + warning) where it makes sense, like in the case with failed
push to upstream you described.
Cheers,
Tomek
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?
> * 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?
> * 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?
>
> Cheers
> André
> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/egit-dev
