How can I avoid "Push Active branches" in Git

Hello Adam,

Press "Push" instead of "Rebase and Push" in the "Push Active Branches" dialog.

I'm using Git with Idea.  One very annoying thing is when I "Commit
and Push" a change, it commits and then comes back with a dialog to
say "Push Active Branches" which gives me the option to "Rebase and
Push".  The actual push doesn't happen until I do "Rebase and Push".
This can take quite a while if I have many modules as it does a rebase
on each of them before pushing out the changes.  Is there any way to
have Commit and Push actually do what it says without all these extra
steps?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Thanks. I didn't see that.

Can I do one better and not have to deal with that dialog at all?  I'd love to just be able to click "Commit and Push" and not be bothered again.  The two step process invites confusion, IMO.  If I want to rebase, I can do that separately.  Why is it tied in with the push process?

Regards,
Adam

Hello Adam,

The workflow that we have now was based on our own experience, where calling
"push" directly has a low probability of success because of changes committed
by other developers in the meantime. That probably doesn't make as much sense
for projects with smaller teams and probably could be made optional, but
right now such an option isn't provided.

Thanks. I didn't see that.

Can I do one better and not have to deal with that dialog at all?  I'd
love to just be able to click "Commit and Push" and not be bothered
again.  The two step process invites confusion, IMO.  If I want to
rebase, I can do that separately.  Why is it tied in with the push
process?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"