summaryrefslogtreecommitdiffstats
path: root/git-gui.sh
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-07-06 04:19:33 +0200
committerShawn O. Pearce <spearce@spearce.org>2007-07-06 10:02:02 +0200
commit87b49a533b0ee0da06c06fb466844885ae0d35bd (patch)
tree394247a67b9726644a312a66ad38d0025a1c9e12 /git-gui.sh
parentgit-gui: Bind M1-P to push action (diff)
downloadgit-87b49a533b0ee0da06c06fb466844885ae0d35bd.tar.xz
git-87b49a533b0ee0da06c06fb466844885ae0d35bd.zip
git-gui: Include a Push action on the left toolbar
Pushing changes to a remote system is a very common action for many users of git-gui, so much so that in some workflows a user is supposed to push immediately after they make a local commit so that their change(s) are immediately available for their teammates to view and build on top of. Including the push button right below the commit button on the left toolbar indicates that users should probably perform this action after they have performed the commit action. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to '')
-rwxr-xr-xgit-gui.sh4
1 files changed, 4 insertions, 0 deletions
diff --git a/git-gui.sh b/git-gui.sh
index c22a431fdb..c38aa067ac 100755
--- a/git-gui.sh
+++ b/git-gui.sh
@@ -1822,6 +1822,10 @@ pack .vpane.lower.commarea.buttons.commit -side top -fill x
lappend disable_on_lock \
{.vpane.lower.commarea.buttons.commit conf -state}
+button .vpane.lower.commarea.buttons.push -text {Push} \
+ -command do_push_anywhere
+pack .vpane.lower.commarea.buttons.push -side top -fill x
+
# -- Commit Message Buffer
#
frame .vpane.lower.commarea.buffer